Crawlora MCP

sonic_item

Read-only

Fetch one Sonic Drive-In menu item detail by path, including name, description, image, and the site-wide nutrition/allergen PDF link. The path must be a menu category, subcategory, or item from sonic_sitemap; use sonic_menu for the full menu or sonic_nutrition_documents for the guide.

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": {
      "path": "<path>"
    },
    "name": "sonic_item"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Required. A "menu" section path from GET /sonic/sitemap (kind item or subcategory).

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds value by disclosing the return payload (name, description, image, nutrition/allergen PDF link), which helps an agent know what it gets back. It does not add anything about rate limits or data freshness, keeping it short of a 5.

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 tight sentences: the first front-loads what is fetched and returned, the second covers valid inputs and routing alternatives. No filler or redundancy.

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?

With an output schema present, the description needn't enumerate every field, yet it names the key ones. Annotations cover the safety profile, and sibling routing is explicit. The only shortfall is the unit-of-path mismatch (category vs. schema's item/subcategory), which leaves a small ambiguity.

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 baseline is 3, and the description mostly restates the path constraint. It does add the sourcing concept ('from sonic_sitemap'), but it also lists 'menu category' as a valid kind while the schema restricts to item/subcategory — a minor inconsistency that slightly muddies rather than clarifies semantics.

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 ('Fetch one Sonic Drive-In menu item detail by path'), enumerates the returned fields, and explicitly distinguishes itself from sonic_menu and sonic_nutrition_documents. An agent can identify the tool without opening the schema.

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?

Explicitly names the alternative ('use sonic_menu for the full menu') and the companion source ('sonic_nutrition_documents for the guide'), and states where the path must come from (sonic_sitemap). When-to-use and when-not-to-use are both covered.

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

All Crawlora MCP tools Inspect

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

Need Help?