Skip to main content
Glama

crawl_status

Read-onlyIdempotent

Returns a structured, read-only snapshot of crawl state, including what is being crawled, what comes next, per-source outcomes, and recent runs—no manual database query needed.

Instructions

Return a structured snapshot of crawl state (on-demand visibility).

Answers "what is the scraw doing / what will it crawl" without a manual DB query. Datasource-centric, matching the daily digest. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
hoursNoWindow for per-source fetch outcome counts (default 24).
run_limitNoHow many recent policy_runs to return (default 20).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Read-only' in the description is largely redundant. The added value is modest: 'snapshot' signals point-in-time state and 'datasource-centric, matching the daily digest' hints at output organization, but pagination, freshness, and cost of the query are unaddressed.

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?

Four short sentences with the core purpose front-loaded and no filler. Minor blemish: the typo 'scraw' and a restated 'Read-only' that duplicates annotations.

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?

An output schema exists, so return values need not be explained, and both optional parameters are fully described in the schema with annotations covering the safety profile. The description supplies the framing (snapshot, datasource-centric, on-demand vs digest) an agent needs to choose it correctly.

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%, so both parameters (hours window, run_limit) are already documented in the schema. The description adds no further meaning about how these interact with the datasource-centric view, so baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource — 'Return a structured snapshot of crawl state' — and frames it as on-demand visibility versus the daily digest. It does not explicitly name a sibling such as plan_crawl, so the differentiation from alternatives is only partial.

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

Usage Guidelines3/5

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

Implies usage through 'on-demand visibility' and 'without a manual DB query', which tells an agent this is the ad-hoc inspection path. There is no explicit when-not guidance or named alternative for planning a crawl versus observing one.

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