Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

sonic_sitemap

Read-only

Fetch one page from Sonic Drive-In's menu-page or store-locator sitemap. Use sonic_categories or sonic_locations for structured catalog and store discovery.

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": {
      "section": "<section>"
    },
    "name": "sonic_sitemap"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOptional. Filter by page kind. menu: index, category, subcategory, item. locations: index, state, city, store. Default all kinds for the chosen section.
pageNoOptional. 1-based page, default 1.
sectionYesRequired. Which sitemap to read: menu (category/subcategory/item pages) or locations (store directory pages).
page_sizeNoOptional. Entries per page, 1-500, default 100.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true) and open-world reach. The description adds the non-obvious framing that this reads a paged sitemap ('Fetch one page'), which tells the agent output is paginated index entries rather than resolved catalog data. No contradiction, and it enriches beyond the annotations.

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

Conciseness5/5

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

Two sentences, zero waste, with the tool's action and scope front-loaded before the sibling-routing sentence. Nothing is repeated from annotations or schema.

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?

An output schema exists, so return values need no explanation, and annotations cover safety. Purpose, scope, and sibling routing are all present; only a slightly richer when-to-use statement would make it fully complete.

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 section/kind/page/page_size are already fully documented in the schema. The description adds no param-level syntax or format detail beyond what the schema states. Baseline 3 is correct when the schema carries the parameter burden.

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?

Specific verb (Fetch) plus specific resource (one page from Sonic's menu-page or store-locator sitemap). It also names the sibling tools that handle structured lookups, so an agent can distinguish this raw-sitemap pager from catalog/store tools without opening any schema.

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?

Explicitly routes the agent to sonic_categories or sonic_locations for structured catalog/store discovery, which implicitly defines when this tool is the right choice (raw sitemap enumeration). It stops short of stating exclusions or a fuller when-to-use scenario, but the alternative routing is clear.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources