Crawlora MCP

sonic_availability

Read-only

List Sonic Drive-In order-ahead windows for one store_id, grouped by channel and local date, with UTC start/end times, store timezone, and timing buffers. fulfillment accepts PICKUP or DELIVERY; returned service_type is a separate finer channel vocabulary. service_types includes supported channels even when they have no current windows. Closed or fully booked stores return an empty channels array; unknown stores return 404. Use sonic_nearby to discover restaurant identifiers.

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": {
      "store_id": "<store_id>"
    },
    "name": "sonic_availability"
  }
}

Input Schema

Name	Required	Description	Default
`store_id`	Yes	Required. A Sonic store number, e.g. from GET /sonic/nearby's store_id.
`fulfillment`	No	Fulfillment method: PICKUP or DELIVERY. Defaults to PICKUP.

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.1/5.0

Behavior4/5

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

With readOnlyHint and openWorldHint already declaring the safety profile, the description adds genuine behavioral context: error semantics (empty channels array when closed/fully booked, 404 for unknown stores) and return framing (UTC times, store timezone, buffers). These are not derivable from 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.

Conciseness4/5

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

Front-loaded with purpose and packed with information-dense sentences; the routing hint is placed last, which is sensible. It is slightly long but each clause carries distinct content (return framing, error behavior, alternative tool).

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 needn't be explained in depth, yet the description usefully adds the closed/fully-booked and 404 edge cases. For a two-parameter lookup with full annotation and schema coverage, this is complete enough to call 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 are already documented, including the PICKUP/DELIVERY values and PICKUP default, which the description largely restates. The service_type clarification concerns output vocabulary rather than input semantics, so it adds little beyond the schema baseline.

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 (List) and resource (Sonic Drive-In order-ahead windows) scoped to one store_id, and the grouping/timezone framing makes it instantly distinguishable from siblings like sonic_store or sonic_menu. An agent knows exactly what it returns 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 Guidelines4/5

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

Explicitly routes the agent to sonic_nearby for discovering restaurant identifiers, which is a real usage prerequisite. It does not spell out when-not-to-use this tool versus other Sonic endpoints (e.g. menu/location tools), so it stops short of the full when/when-not/alternatives picture.

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?