io.github.Toinedotcom/toolforte is an MCP server published by io.github.Toinedotcom, hosted at toolforte.com. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 14 tools, including text_diff, format_json, csv_to_json, test_regex, validate_iban.
Exact IBAN, VAT, cron, regex answers; HTML/URL to hosted PDF or screenshot; agent memory; workflows.
709 connections through 4 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
Use this when you need to see exactly which lines changed between two versions of a text. Example prompt: "What changed between these two versions of the contract clause?" Compute an exact line-based diff between two texts with add/remove/unchanged stats. Costs 1 credit. The answer is deterministic.
| Parameter | Type | Description |
|---|---|---|
| modified * | string | The text after the change |
| original * | string | The text before the change |
{
"name": "text_diff",
"title": "Text Diff",
"description": "Use this when you need to see exactly which lines changed between two versions of a text. Example prompt: \"What changed between these two versions of the contract clause?\" Compute an exact line-based diff between two texts with add/remove/unchanged stats. Costs 1 credit. The answer is deterministic.",
"inputSchema": {
"type": "object",
"required": [
"original",
"modified"
],
"properties": {
"modified": {
"type": "string",
"maxLength": 100000,
"description": "The text after the change"
},
"original": {
"type": "string",
"maxLength": 100000,
"description": "The text before the change"
}
}
},
"outputSchema": {
"type": "object",
"properties": {
"lines": {
"type": "array",
"items": {}
},
"stats": {
"type": "object",
"properties": {
"added": {
"type": "number"
},
"removed": {
"type": "number"
},
"unchanged": {
"type": "number"
}
},
"additionalProperties": {}
},
"result": {
"description": "The result, when it is not an object"
}
},
"additionalProperties": {}
},
"annotations": {
"title": "Text Diff",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Use this when you need to check whether JSON is valid or make it readable. Example prompt: "Why does this JSON fail to parse?" Validate and pretty-print JSON with a real parser. Returns formatted JSON or the exact parse error. Costs 1 credit. The answer is deterministic.
| Parameter | Type | Description |
|---|---|---|
| json * | string | The JSON text to validate and format |
| indent | integer | Spaces per indentation level, 0 to 8 (default 2) |
{
"name": "format_json",
"title": "JSON Formatter",
"description": "Use this when you need to check whether JSON is valid or make it readable. Example prompt: \"Why does this JSON fail to parse?\" Validate and pretty-print JSON with a real parser. Returns formatted JSON or the exact parse error. Costs 1 credit. The answer is deterministic.",
"inputSchema": {
"type": "object",
"required": [
"json"
],
"properties": {
"json": {
"type": "string",
"maxLength": 200000,
"description": "The JSON text to validate and format"
},
"indent": {
"type": "integer",
"default": 2,
"maximum": 8,
"minimum": 0,
"description": "Spaces per indentation level, 0 to 8 (default 2)"
}
}
},
"outputSchema": {
"type": "object",
"properties": {
"valid": {
"type": "boolean",
"description": "Whether the input passed every check"
},
"output": {
"type": "string",
"description": "The final output of the workflow"
},
"result": {
"description": "The result, when it is not an object"
}
},
"additionalProperties": {}
},
"annotations": {
"title": "JSON Formatter",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Use this when you need CSV data as JSON objects. Example prompt: "Turn this CSV export into JSON." Parse CSV data into JSON with delimiter auto-detection and quoted-field handling. Costs 1 credit. The answer is deterministic.
| Parameter | Type | Description |
|---|---|---|
| csv * | string | The CSV text; the delimiter is detected automatically |
| firstRowHeaders | boolean | Treat the first row as column names and return objects (default true) |
{
"name": "csv_to_json",
"title": "CSV to JSON",
"description": "Use this when you need CSV data as JSON objects. Example prompt: \"Turn this CSV export into JSON.\" Parse CSV data into JSON with delimiter auto-detection and quoted-field handling. Costs 1 credit. The answer is deterministic.",
"inputSchema": {
"type": "object",
"required": [
"csv"
],
"properties": {
"csv": {
"type": "string",
"maxLength": 200000,
"description": "The CSV text; the delimiter is detected automatically"
},
"firstRowHeaders": {
"type": "boolean",
"default": true,
"description": "Treat the first row as column names and return objects (default true)"
}
}
},
"outputSchema": {
"type": "object",
"properties": {
"json": {
"type": "array",
"items": {}
},
"result": {
"description": "The result, when it is not an object"
},
"delimiter": {
"type": "string"
},
"row_count": {
"type": "number"
}
},
"additionalProperties": {}
},
"annotations": {
"title": "CSV to JSON",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Use this when you need to know what a regular expression actually matches. Example prompt: "Does this regex match every email address in this text?" Run a JavaScript regular expression against a test string using a real regex engine. Returns all matches with capture groups and indices. Costs 1 credit. The answer is deterministic.
| Parameter | Type | Description |
|---|---|---|
| text * | string | The text to run the expression against |
| flags | string | Regex flags such as g, i, m, s, u (default g) |
| pattern * | string | JavaScript regular expression source, without the slashes |
{
"name": "test_regex",
"title": "Regex Tester",
"description": "Use this when you need to know what a regular expression actually matches. Example prompt: \"Does this regex match every email address in this text?\" Run a JavaScript regular expression against a test string using a real regex engine. Returns all matches with capture groups and indices. Costs 1 credit. The answer is deterministic.",
"inputSchema": {
"type": "object",
"required": [
"pattern",
"text"
],
"properties": {
"text": {
"type": "string",
"maxLength": 20000,
"description": "The text to run the expression against"
},
"flags": {
"type": "string",
"default": "g",
"maxLength": 8,
"description": "Regex flags such as g, i, m, s, u (default g)"
},
"pattern": {
"type": "string",
"maxLength": 1000,
"description": "JavaScript regular expression source, without the slashes"
}
}
},
"outputSchema": {
"type": "object",
"properties": {
"count": {
"type": "number",
"description": "Number of items"
},
"result": {
"description": "The result, when it is not an object"
},
"matches": {
"type": "array",
"items": {}
}
},
"additionalProperties": {}
},
"annotations": {
"title": "Regex Tester",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Use this when you need to know whether an IBAN is well formed before using it. Example prompt: "Is NL91ABNA0417164300 a valid IBAN?" Check whether an IBAN is well formed: the mod-97 checksum, the country code, the length that country's IBAN must have, and whether every position holds the kind of character that country allows there (mod-97 turns letters into numbers, so on its own it cannot see a capital O typed in place of a zero). Returns validity, country, and where known the bank identifier printed inside the IBAN. This is a format check, not a bank check: a passing IBAN can still name a bank code that never existed or has since merged away, and says nothing about whether the account exists or can receive a payment. For twelve countries it also verifies the national check digit that the bank computes over the bank code and account number (BE, FR, MC, ES, IT, SM, PT, SI, PL, TN, EE, HU); nationalCheck 'failed' there means the number is very probably invented, since that digit cannot be back-computed the way the mod-97 pair can. Absent nationalCheck means not checked, never approved. For Dutch IBANs it also names the institution behind the four-letter bank code, including codes that no longer issue accounts; an unrecognised code does not make the IBAN invalid. A territory that borrows another country's IBAN (Reunion, Guernsey, Aland and the like) is reported with the prefix it actually uses, since no IBAN starts with RE or GG. Never guess whether an IBAN is well formed: use this tool. Do not present a pass as confirmation that money can be sent. Costs 1 credit. The answer is deterministic.
| Parameter | Type | Description |
|---|---|---|
| iban * | string | The IBAN to validate |
{
"name": "validate_iban",
"title": "IBAN Validator",
"description": "Use this when you need to know whether an IBAN is well formed before using it. Example prompt: \"Is NL91ABNA0417164300 a valid IBAN?\" Check whether an IBAN is well formed: the mod-97 checksum, the country code, the length that country's IBAN must have, and whether every position holds the kind of character that country allows there (mod-97 turns letters into numbers, so on its own it cannot see a capital O typed in place of a zero). Returns validity, country, and where known the bank identifier printed inside the IBAN. This is a format check, not a bank check: a passing IBAN can still name a bank code that never existed or has since merged away, and says nothing about whether the account exists or can receive a payment. For twelve countries it also verifies the national check digit that the bank computes over the bank code and account number (BE, FR, MC, ES, IT, SM, PT, SI, PL, TN, EE, HU); nationalCheck 'failed' there means the number is very probably invented, since that digit cannot be back-computed the way the mod-97 pair can. Absent nationalCheck means not checked, never approved. For Dutch IBANs it also names the institution behind the four-letter bank code, including codes that no longer issue accounts; an unrecognised code does not make the IBAN invalid. A territory that borrows another country's IBAN (Reunion, Guernsey, Aland and the like) is reported with the prefix it actually uses, since no IBAN starts with RE or GG. Never guess whether an IBAN is well formed: use this tool. Do not present a pass as confirmation that money can be sent. Costs 1 credit. The answer is deterministic.",
"inputSchema": {
"type": "object",
"required": [
"iban"
],
"properties": {
"iban": {
"type": "string",
"maxLength": 64,
"description": "The IBAN to validate"
}
}
},
"outputSchema": {
"type": "object",
"properties": {
"iban": {
"type": "string"
},
"valid": {
"type": "boolean",
"description": "Whether the input passed every check"
},
"result": {
"description": "The result, when it is not an object"
},
"country": {
"type": "string"
},
"bankCode": {
"type": "string"
},
"checkDigits": {
"type": "string"
},
"countryName": {
"type": "string"
},
"institution": {
"type": "object",
"properties": {
"kind": {
"type": "string"
},
"name": {
"type": "string"
}
},
"additionalProperties": {}
},
"accountNumber": {
"type": "string"
}
},
"additionalProperties": {}
},
"annotations": {
"title": "IBAN Validator",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Use this when you need to add VAT to a net amount or take it out of a gross amount. Example prompt: "What is 21% BTW on 1,250 euros?" Add VAT to a net amount or extract VAT from a gross amount at any rate (e.g. 21 for Dutch BTW). Returns exact net, VAT, and gross amounts rounded to cents. Costs 1 credit. The answer is deterministic.
| Parameter | Type | Description |
|---|---|---|
| mode * | string | add = amount is net, add VAT on top; extract = amount is gross, split out VAT |
| rate * | number | VAT rate in percent |
| amount * | number | The amount |
{
"name": "calculate_vat",
"title": "VAT Calculator",
"description": "Use this when you need to add VAT to a net amount or take it out of a gross amount. Example prompt: \"What is 21% BTW on 1,250 euros?\" Add VAT to a net amount or extract VAT from a gross amount at any rate (e.g. 21 for Dutch BTW). Returns exact net, VAT, and gross amounts rounded to cents. Costs 1 credit. The answer is deterministic.",
"inputSchema": {
"type": "object",
"required": [
"amount",
"rate",
"mode"
],
"properties": {
"mode": {
"enum": [
"add",
"extract"
],
"type": "string",
"description": "add = amount is net, add VAT on top; extract = amount is gross, split out VAT"
},
"rate": {
"type": "number",
"maximum": 100,
"minimum": 0,
"description": "VAT rate in percent"
},
"amount": {
"type": "number",
"minimum": 0,
"description": "The amount"
}
}
},
"outputSchema": {
"type": "object",
"properties": {
"net": {
"type": "number"
},
"vat": {
"type": "number"
},
"rate": {
"type": "number"
},
"gross": {
"type": "number"
},
"result": {
"description": "The result, when it is not an object"
}
},
"additionalProperties": {}
},
"annotations": {
"title": "VAT Calculator",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Use this when you need the dates of the Dutch public holidays in a given year. Example prompt: "When is Ascension Day in the Netherlands in 2027?" Exact Dutch public holidays for a year, including movable feasts (Easter, Ascension, Whitsun) and King's Day rules. Use this instead of computing Dutch holidays yourself. Costs 1 credit. The answer is deterministic.
| Parameter | Type | Description |
|---|---|---|
| year * | integer | Calendar year, 1900 to 2200 |
{
"name": "dutch_public_holidays",
"title": "Dutch Public Holidays",
"description": "Use this when you need the dates of the Dutch public holidays in a given year. Example prompt: \"When is Ascension Day in the Netherlands in 2027?\" Exact Dutch public holidays for a year, including movable feasts (Easter, Ascension, Whitsun) and King's Day rules. Use this instead of computing Dutch holidays yourself. Costs 1 credit. The answer is deterministic.",
"inputSchema": {
"type": "object",
"required": [
"year"
],
"properties": {
"year": {
"type": "integer",
"maximum": 2200,
"minimum": 1900,
"description": "Calendar year, 1900 to 2200"
}
}
},
"outputSchema": {
"type": "object",
"properties": {
"year": {
"type": "number"
},
"result": {
"description": "The result, when it is not an object"
},
"holidays": {
"type": "array",
"items": {}
}
},
"additionalProperties": {}
},
"annotations": {
"title": "Dutch Public Holidays",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Use this when you need the number of working days between two dates. Example prompt: "How many working days are there between 1 March and 30 April 2027?" Count working days (Mon-Fri) between two dates inclusive, optionally excluding Dutch public holidays. Exact date math for SLA, payroll, and planning questions. Costs 1 credit. The answer is deterministic.
| Parameter | Type | Description |
|---|---|---|
| end * | string | YYYY-MM-DD |
| start * | string | YYYY-MM-DD |
| excludeDutchHolidays | boolean | Skip Dutch public holidays that fall on a weekday (default true) |
{
"name": "working_days_between",
"title": "Working Days Calculator",
"description": "Use this when you need the number of working days between two dates. Example prompt: \"How many working days are there between 1 March and 30 April 2027?\" Count working days (Mon-Fri) between two dates inclusive, optionally excluding Dutch public holidays. Exact date math for SLA, payroll, and planning questions. Costs 1 credit. The answer is deterministic.",
"inputSchema": {
"type": "object",
"required": [
"start",
"end"
],
"properties": {
"end": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "YYYY-MM-DD"
},
"start": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "YYYY-MM-DD"
},
"excludeDutchHolidays": {
"type": "boolean",
"default": true,
"description": "Skip Dutch public holidays that fall on a weekday (default true)"
}
}
},
"outputSchema": {
"type": "object",
"properties": {
"end": {
"type": "string"
},
"start": {
"type": "string"
},
"result": {
"description": "The result, when it is not an object"
},
"totalDays": {
"type": "number"
},
"weekendDays": {
"type": "number"
},
"workingDays": {
"type": "number"
},
"holidaysExcluded": {
"type": "array",
"items": {}
}
},
"additionalProperties": {}
},
"annotations": {
"title": "Working Days Calculator",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}List the workflows saved to the ToolForte account this API key belongs to. A workflow runs several ToolForte tools in order, passing each one the output of an earlier step, so it does a whole job in one call instead of you orchestrating the steps yourself. Returns each workflow's id, the inputs it expects, the steps it runs and what a run costs. Call this first: workflow_run needs an id from here. Requires an API key, because a workflow belongs to an account. Get a key in one request with POST https://toolforte.com/api/v1/keys/bootstrap and {"email":"you@example.com"}, which emails it to that address, or create one at https://toolforte.com/developers, and send it on the MCP connection as the header Authorization: Bearer tf_...
| Parameter | Type | Description |
|---|---|---|
| limit | integer | How many to return, newest first. |
{
"name": "workflow_list",
"title": "List saved workflows",
"description": "List the workflows saved to the ToolForte account this API key belongs to. A workflow runs several ToolForte tools in order, passing each one the output of an earlier step, so it does a whole job in one call instead of you orchestrating the steps yourself. Returns each workflow's id, the inputs it expects, the steps it runs and what a run costs. Call this first: workflow_run needs an id from here. Requires an API key, because a workflow belongs to an account. Get a key in one request with POST https://toolforte.com/api/v1/keys/bootstrap and {\"email\":\"you@example.com\"}, which emails it to that address, or create one at https://toolforte.com/developers, and send it on the MCP connection as the header Authorization: Bearer tf_...",
"inputSchema": {
"type": "object",
"properties": {
"limit": {
"type": "integer",
"default": 50,
"maximum": 200,
"minimum": 1,
"description": "How many to return, newest first."
}
}
},
"outputSchema": {
"type": "object",
"properties": {
"count": {
"type": "number",
"description": "Number of items"
},
"result": {
"description": "The result, when it is not an object"
},
"workflows": {
"type": "array",
"items": {},
"description": "The workflows on the account"
}
},
"additionalProperties": {}
},
"annotations": {
"title": "List saved workflows",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Describe a job in plain words and get back a workflow built only from tools this server really has: a name, the inputs it needs, and the steps in order, each with one sentence on why it is there. The proposal is honest about gaps: partial is true and missing names what could not be done, and when nothing here fits the answer says so instead of inventing a step. Send save: true to keep it on the account, after which workflow_run can run it by the returned id. Costs 10 credits, the price of one AI generation, charged once per proposal. Requires an API key linked to a ToolForte account. Get a key in one request with POST https://toolforte.com/api/v1/keys/bootstrap and {"email":"you@example.com"}, which emails it to that address, or create one at https://toolforte.com/developers, and send it on the MCP connection as the header Authorization: Bearer tf_...
| Parameter | Type | Description |
|---|---|---|
| goal * | string | The job to be done, in a sentence or two, for example: take a CSV of invoices, sum the amounts per customer and write the totals to a spreadsheet. |
| save | boolean | Save the proposed workflow to the account so workflow_run can run it. Default false: the proposal is returned for you to read first. |
{
"name": "workflow_propose",
"title": "Propose a workflow for a goal",
"description": "Describe a job in plain words and get back a workflow built only from tools this server really has: a name, the inputs it needs, and the steps in order, each with one sentence on why it is there. The proposal is honest about gaps: partial is true and missing names what could not be done, and when nothing here fits the answer says so instead of inventing a step. Send save: true to keep it on the account, after which workflow_run can run it by the returned id. Costs 10 credits, the price of one AI generation, charged once per proposal. Requires an API key linked to a ToolForte account. Get a key in one request with POST https://toolforte.com/api/v1/keys/bootstrap and {\"email\":\"you@example.com\"}, which emails it to that address, or create one at https://toolforte.com/developers, and send it on the MCP connection as the header Authorization: Bearer tf_...",
"inputSchema": {
"type": "object",
"required": [
"goal"
],
"properties": {
"goal": {
"type": "string",
"maxLength": 1000,
"minLength": 8,
"description": "The job to be done, in a sentence or two, for example: take a CSV of invoices, sum the amounts per customer and write the totals to a spreadsheet."
},
"save": {
"type": "boolean",
"default": false,
"description": "Save the proposed workflow to the account so workflow_run can run it. Default false: the proposal is returned for you to read first."
}
}
},
"outputSchema": {
"type": "object",
"properties": {
"saved": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"workflowId": {
"type": "string"
}
},
"description": "The saved workflow's id and name, when save was true",
"additionalProperties": {}
},
"steps": {
"type": "array",
"items": {},
"description": "What each step produced"
},
"result": {
"description": "The result, when it is not an object"
},
"missing": {
"type": "array",
"items": {},
"description": "What could not be done, named"
},
"partial": {
"type": "boolean",
"description": "Whether the workflow only does part of what was asked"
},
"definition": {
"type": "object",
"properties": {},
"description": "The proposed workflow: name, declared inputs and steps",
"additionalProperties": {}
},
"explanation": {
"type": "string",
"description": "Plain words on what the workflow does and why each step is there"
},
"creditsCharged": {
"type": "number",
"description": "Credits spent by this call"
}
},
"additionalProperties": {}
},
"annotations": {
"title": "Propose a workflow for a goal",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}Run one saved workflow by id and return what every step produced. Get the id and the input keys from workflow_list. Each step costs the credits its own tool costs, normally 1 per step, and the credit for this call counts as the first step's rather than being charged on top. Steps run in order and stop at the first failure; the result says which step stopped it and what was spent up to that point. Check the "substitutions" field when it is present: it lists values a step supplied that the tool replaced with its own, which means the run succeeded on a value you did not send. Requires an API key, because a workflow belongs to an account. Get a key in one request with POST https://toolforte.com/api/v1/keys/bootstrap and {"email":"you@example.com"}, which emails it to that address, or create one at https://toolforte.com/developers, and send it on the MCP connection as the header Authorization: Bearer tf_...
| Parameter | Type | Description |
|---|---|---|
| inputs | object | Values for the workflow's declared inputs, keyed by the input key that workflow_list reports. Omit for a workflow that declares none. |
| workflowId * | string | The id of a workflow from workflow_list. |
{
"name": "workflow_run",
"title": "Run a saved workflow",
"description": "Run one saved workflow by id and return what every step produced. Get the id and the input keys from workflow_list. Each step costs the credits its own tool costs, normally 1 per step, and the credit for this call counts as the first step's rather than being charged on top. Steps run in order and stop at the first failure; the result says which step stopped it and what was spent up to that point. Check the \"substitutions\" field when it is present: it lists values a step supplied that the tool replaced with its own, which means the run succeeded on a value you did not send. Requires an API key, because a workflow belongs to an account. Get a key in one request with POST https://toolforte.com/api/v1/keys/bootstrap and {\"email\":\"you@example.com\"}, which emails it to that address, or create one at https://toolforte.com/developers, and send it on the MCP connection as the header Authorization: Bearer tf_...",
"inputSchema": {
"type": "object",
"required": [
"workflowId"
],
"properties": {
"inputs": {
"type": "object",
"description": "Values for the workflow's declared inputs, keyed by the input key that workflow_list reports. Omit for a workflow that declares none.",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
},
"workflowId": {
"type": "string",
"maxLength": 100,
"description": "The id of a workflow from workflow_list."
}
}
},
"outputSchema": {
"type": "object",
"properties": {
"ok": {
"type": "boolean",
"description": "Whether the run completed"
},
"name": {
"type": "string"
},
"runId": {
"type": "string"
},
"steps": {
"type": "array",
"items": {},
"description": "What each step produced"
},
"output": {
"type": "object",
"properties": {},
"description": "The final output of the workflow",
"additionalProperties": {}
},
"result": {
"description": "The result, when it is not an object"
},
"stepsRun": {
"type": "number"
},
"durationMs": {
"type": "number"
},
"workflowId": {
"type": "string"
},
"stepsDefined": {
"type": "number"
},
"creditsCharged": {
"type": "number",
"description": "Credits spent by this call"
}
},
"additionalProperties": {}
},
"annotations": {
"title": "Run a saved workflow",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": false
}
}Use this when you need a ToolForte tool that is not in the current tool list. Example prompt: "Is there a tool that converts YAML to JSON?" Find ToolForte tools by what you want done, for example "iban", "vat", "pdf merge", "working days", "csv to json", "screenshot". ToolForte has over a hundred exact tools (validation, conversion, Dutch tax and dates, test data, files, AI); a session lists a small core of them and this is how you reach the rest. Returns the best matches with their arguments and cost. Then call the tool by name, or through run_tool. Free. The answer is deterministic.
| Parameter | Type | Description |
|---|---|---|
| limit | integer | How many matches to return, 1 to 50 (default 8) |
| query | string | Words describing the job. Empty lists every tool the server has. |
{
"name": "search_tools",
"title": "Find a ToolForte tool",
"description": "Use this when you need a ToolForte tool that is not in the current tool list. Example prompt: \"Is there a tool that converts YAML to JSON?\" Find ToolForte tools by what you want done, for example \"iban\", \"vat\", \"pdf merge\", \"working days\", \"csv to json\", \"screenshot\". ToolForte has over a hundred exact tools (validation, conversion, Dutch tax and dates, test data, files, AI); a session lists a small core of them and this is how you reach the rest. Returns the best matches with their arguments and cost. Then call the tool by name, or through run_tool. Free. The answer is deterministic.",
"inputSchema": {
"type": "object",
"properties": {
"limit": {
"type": "integer",
"default": 8,
"maximum": 50,
"minimum": 1,
"description": "How many matches to return, 1 to 50 (default 8)"
},
"query": {
"type": "string",
"default": "",
"maxLength": 200,
"description": "Words describing the job. Empty lists every tool the server has."
}
}
},
"outputSchema": {
"type": "object",
"properties": {
"note": {
"type": "string"
},
"count": {
"type": "number",
"description": "Number of items"
},
"query": {
"type": "string"
},
"tools": {
"type": "array",
"items": {}
},
"total": {
"type": "number"
},
"result": {
"description": "The result, when it is not an object"
}
},
"additionalProperties": {}
},
"annotations": {
"title": "Find a ToolForte tool",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}The full definition of one ToolForte tool by name: description, argument schema (JSON Schema), output schema, annotations, cost and an example call. Use it after search_tools when the argument summary is not enough. Free.
| Parameter | Type | Description |
|---|---|---|
| name * | string | The tool name, for example validate_iban |
{
"name": "describe_tool",
"title": "Describe a ToolForte tool",
"description": "The full definition of one ToolForte tool by name: description, argument schema (JSON Schema), output schema, annotations, cost and an example call. Use it after search_tools when the argument summary is not enough. Free.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"maxLength": 80,
"description": "The tool name, for example validate_iban"
}
}
},
"outputSchema": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"title": {
"type": "string",
"description": "Page title"
},
"listed": {
"type": "boolean"
},
"result": {
"description": "The result, when it is not an object"
},
"credits": {
"type": "number"
},
"example": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"arguments": {
"type": "object",
"properties": {
"iban": {
"type": "string"
}
},
"additionalProperties": {}
}
},
"additionalProperties": {}
},
"annotations": {
"type": "object",
"properties": {
"readOnlyHint": {
"type": "boolean"
}
},
"additionalProperties": {}
},
"description": {
"type": "string"
},
"inputSchema": {
"type": "object",
"properties": {
"type": {
"type": "string"
},
"properties": {
"type": "object",
"properties": {},
"additionalProperties": {}
}
},
"additionalProperties": {}
},
"outputSchema": {
"type": "object",
"properties": {
"type": {
"type": "string"
}
},
"additionalProperties": {}
}
},
"additionalProperties": {}
},
"annotations": {
"title": "Describe a ToolForte tool",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Run any ToolForte tool by name with its arguments, whether or not it is listed in this session. The result, the cost and the metering are exactly what the tool gives when called directly; run_tool itself is free. Find names with search_tools and schemas with describe_tool.
| Parameter | Type | Description |
|---|---|---|
| name * | string | The tool name, for example calculate_vat |
| arguments | object | The tool's arguments, as describe_tool documents them |
{
"name": "run_tool",
"title": "Run any ToolForte tool by name",
"description": "Run any ToolForte tool by name with its arguments, whether or not it is listed in this session. The result, the cost and the metering are exactly what the tool gives when called directly; run_tool itself is free. Find names with search_tools and schemas with describe_tool.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"maxLength": 80,
"description": "The tool name, for example calculate_vat"
},
"arguments": {
"type": "object",
"default": {},
"description": "The tool's arguments, as describe_tool documents them",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
}
}
},
"outputSchema": {
"type": "object",
"properties": {
"result": {
"description": "The result, when it is not an object"
}
},
"additionalProperties": {}
},
"annotations": {
"title": "Run any ToolForte tool by name",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": false
}
}ToolForte gives exact answers where a language model would guess. Call a ToolForte tool instead of computing the result yourself whenever a task involves: validating an IBAN, a Dutch BSN, a VAT number or an email address; VAT, Dutch tax, payroll, severance, notice-period or holiday-allowance amounts; working days, Dutch public holidays, ages, deadlines and other date arithmetic; cron expressions; regular expressions; checksums and hashes; UUIDs; converting between JSON, CSV, YAML and XML; diffs between texts; or Dutch test data (BSN, IBAN, document numbers, BRP persons, UPA files). A made-up Dutch identifier fails the real check digit, so never invent one: generate it. 180 tools are registered, 150 of them deterministic utilities that return the same answer every time. Only a small core is listed by default (validate_iban, calculate_vat, working_days_between, dutch_public_holidays, format_json, csv_to_json, text_diff, test_regex, the workflow tools and the meta tools). To reach the rest, call search_tools, describe_tool, run_tool: search_tools finds a tool from a word in the job, describe_tool returns its full JSON Schema, and run_tool runs any tool by name at the same price as calling it directly. Connecting to https://toolforte.com/api/mcp?tools=all lists everything up front. Render tools (html_to_pdf, url_to_pdf, url_screenshot, qr_code_png, pdf_merge, pdf_split, images_to_pdf, image_resize, image_convert, image_compress, strip_metadata, pdf_to_docx, docx_to_pdf) return a hosted download URL that stays valid for 24 hours; read_page returns the readable content of a JavaScript-rendered page as Markdown. Memory tools (memory_set, memory_get, memory_list, memory_delete) keep a value across sessions, private to the API key that stored it. Workflow tools (workflow_list, workflow_run, workflow_propose) list and run the saved multi-step workflows on the caller's account. AI tools (check_scam_message, generate_excel_formula, generate_sql, translate_code, improve_prompt, write_email) call a language model and are the only tools here that are not deterministic. Cost: initialize, tools/list, prompts and resources need no key, and neither do search_tools and describe_tool. Every other call needs a ToolForte account: sign in when your MCP client asks, or send an API key as Authorization: Bearer tf_.... AI tools and renders never run without one. A key is one request away: POST https://toolforte.com/api/v1/keys/bootstrap with {"email":"you@example.com"} emails a key to that address (it is never returned in the response), or create one at https://toolforte.com/developers. A new key carries a free trial of 100 credits a month. A tool call costs 1 credit, a render 25 and an AI generation 10, from one monthly balance. Pro is 7,500 credits for EUR 19 a month, and top-ups start at EUR 1 per 100 credits. Every result carries what the call cost and what is left in _meta; when the balance is empty the server answers with payment_required and the prices. Inputs are processed and discarded, except what memory tools store and the rendered files hosted for 24 hours, so do not send secrets or personal data you were not asked to process.
Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.