Forecall
Failure recordsDocs

Score your MCP tool descriptions

Paste the JSON your MCP server returns for tools/list, or choose a file. Each tool's description is scored out of 100.

No JSON at hand?See a sample resultGet it with the CLI

Accepted formats

An array of tools
[{ "name": … }, …]
An object with a tools array
{ "tools": [ … ] }
A JSON-RPC response
{ "result": { "tools": [ … ] } }
A list of entries that is not a tools/list, such as search results or endpoints (also results, items, endpoints, or a bare array), each with a name, id, title or path and a description, summary, text or snippet
{ "entries": [{ "id": …, "summary": … }, …] }

Up to 1 MB (1,048,576 bytes) and 200 tools.

$ forecall lint
If both are given, the file is used.

Do not paste tool definitions that are not public yet.

Anyone with the result URL can see the result. Search engines will not list it, and it is deleted after 30 days.

Or score a public server by its URL

For a Streamable HTTP server that needs no sign-in: we ask it for its tools/list and score the answer, as forecall dump does.

We send that server one initialize request and the tools/list requests, from our own server, and nothing about you, not even your IP address. What it returns is kept with the result for 30 days, like pasted JSON. Up to 10 times an hour.

Get your tools/list with the CLI

The CLI starts your server, asks it for tools/list and writes tools.json. Score that file on your machine, or paste it above for a result you can share.

Terminal · Node.js 22 or later
  1. npx forecall dump -o tools.json -- <start command>
  2. npx forecall lint tools.json
Remote servers and other options