Skip to main content
Glama

readfetch

readfetch_crawl_status

Read-only

FREE — no payment or wallet: Poll a crawl job started with readfetch_crawl. FREE — no payment or wallet; unauthenticated. Pass id from the crawl response. Returns job_id, status (queued, running, complete, or failed), completed/total counts, and a growing pages list (url plus Markdown) as results land. Stop polling when status is complete or failed. Results are kept for one hour after the job finishes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "readfetch_crawl_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesJob id from readfetch_crawl (`job_id` in the start response). Required for MCP tools/call; poll until status is complete or failed (results kept ~1 hour).

Output Schema

NameRequiredDescriptionDefault
pagesNo
totalNo
job_idNo
statusNo
completedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already flag readOnlyHint and openWorldHint, but the description adds genuinely useful facts: no payment or wallet required, it is unauthenticated, pages grow incrementally as results land, and results are retained only one hour after completion. The retention window and the growing-result behavior are exactly the kind of operational context annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The main sentence is front-loaded and well ordered (purpose, auth, input, return, termination, retention), but 'FREE — no payment or wallet' appears twice in near-identical form, wasting space on a repeated claim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple polling tool with an output schema, annotations, and full schema coverage, the description covers everything an agent needs: when to call it, what to pass, how to interpret status, when to stop, and how long results persist.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and there is a single required parameter. The description's 'Pass `id` from the crawl response' merely repeats what the schema already says, adding no format or edge-case detail beyond it, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource — poll a crawl job started with readfetch_crawl — and names the companion tool so an agent can tell it apart from readfetch_crawl (which starts jobs) and the other siblings. It also enumerates what comes back (job_id, status, counts, pages).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives the selection context (only for jobs already started with readfetch_crawl), tells the agent to pass the id from that response, and specifies the termination condition: stop when status is complete or failed. It does not discuss failure recovery or what to do on repeated failed polls, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.