Skip to main content
Glama

Crawlgraph Gap Status

crawlgraph_gap_status
Read-onlyIdempotent

Poll a previously-submitted gap analysis job by ID. Use this when crawlgraph_gap_analysis or crawlgraph_gap_outreach_targets returned status=pending with a job_id, call this with the same job_id to retrieve the result once status=completed. Read-only; no quota cost.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "job_id": "gap_a1b2c3d4e5f6",
      "_apiKey": "your-crawlgraph-api-key"
    },
    "name": "crawlgraph_gap_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe gap job ID (looks like "gap_a1b2c3").
_apiKeyYesCrawlGraph API key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description still adds genuinely new behavior: that this polling call carries no quota cost, which is the key decision factor for whether an agent should poll repeatedly. It stops short of describing the shape of the completed result or what a failed/expired job looks like.

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

Conciseness4/5

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

Three short sentences with the core action front-loaded and no filler. The middle sentence is slightly run-on ('Use this when ... returned status=pending with a job_id, call this with the same job_id') and would read more cleanly split in two, but no information is wasted.

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

Completeness4/5

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

There is no output schema, so the description carries the burden of explaining what comes back, and it only says 'retrieve the result' without describing the result fields or terminal states beyond completed. For a simple two-parameter polling tool this is close to sufficient, with a small gap around failure states.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds real meaning beyond the schema by tying job_id to the value returned by the two submission tools, making the handoff unambiguous. _apiKey is left entirely to the schema, which is acceptable.

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?

States a specific verb and resource: poll a previously-submitted gap analysis job by ID to retrieve its result. It also implicitly distinguishes itself from the submission siblings by calling itself a retrieval/polling step rather than an analysis kickoff.

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

Usage Guidelines5/5

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

Names the two alternatives explicitly (crawlgraph_gap_analysis, crawlgraph_gap_outreach_targets) and the exact precondition that selects this tool: those tools returned status=pending with a job_id. It also states the trigger for actually consuming the result (status=completed) and that the same job_id must be reused.

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.