Skip to main content
Glama
Sign In
xeryuscrawl

xeryuscrawl

by KingXeryus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

crawl_status

Monitor a crawl or batch by checking its progress and retrieving discovered pages 50 at a time from the skip offset.

Instructions

A crawl's or batch's progress and its pages, 50 at a time from skip.

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": {
      "job": "<job>"
    },
    "name": "crawl_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYes
skipNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one valuable trait: results are returned 50 at a time and paginated via `skip`. It says nothing about behavior for an unknown job id, whether in-progress jobs return partial pages, or how completion is signalled.

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?

A single efficient clause with zero filler, and the pagination fact is placed where it is needed. It is arguably too compressed — the sentence lacks a verb and reads as a fragment rather than a statement of action.

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

Completeness3/5

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

For a two-parameter, no-output-schema polling tool, the description covers the core idea and pagination but omits how an agent knows the job finished and what the page entries contain. It is adequate to call the tool, not fully adequate to interpret the result.

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 coverage is 0% for two parameters, so the description must compensate. It explains `skip` well (offset with page size 50) and implies `job` identifies a crawl or batch, but never states whether `job` is an id, a name, or what format it takes.

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?

Names the resource precisely (a crawl's or batch's progress plus its pages) so an agent can tell it apart from `crawl` and `batch_scrape`, which start jobs rather than report on them. It is a noun phrase with no verb, so it stops short of a fully explicit 'return the status of...' statement.

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?

Mentioning 'crawl's or batch's progress' implies the polling use case after a crawl or batch job is started, but there is no explicit 'use when' instruction, no note on when to stop polling, and no named alternative. Usage is inferable rather than stated.

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

Deploy Server

Other Tools