Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sonic_availability

Check Sonic Drive-In order-ahead time slots by store ID. Returns available pickup or delivery windows, service channels, timezone, and slot duration; closed stores return empty results, not errors.

Instructions

List a Sonic Drive-In restaurant's order-ahead time slots. Returns the bookable order-ahead windows for one Sonic Drive-In restaurant, grouped by service channel and local date. Each window has a UTC start_time and end_time. Also returns the store's timezone, how long each window lasts (slot_duration_minutes), the prep/handoff buffer before the first bookable window (lead_time_minutes), and service_types -- every channel the store supports, which is a superset of the channels that currently have windows. fulfillment selects the request method and accepts exactly PICKUP or DELIVERY; note the per-window service_type is a separate, finer vocabulary and can be ORDER_AHEAD, CURBSIDE_PICKUP, DRIVE_THROUGH, STORE, PICKUP or DELIVERY. A closed or fully-booked restaurant returns an empty channels array with total_slots 0, not an error. An unknown store_id returns 404.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
store_idYesSonic store number, e.g. from /sonic/nearby
fulfillmentNoFulfillment method: PICKUP or DELIVERY. Defaults to PICKUP.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / fulfillment / enum
      Added value: +[
+  "PICKUP",
+  "DELIVERY"
+]
  2. Addedv1.16.2

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full disclosure burden and does so thoroughly. It describes the timezone, slot_duration_minutes, lead_time_minutes, service_types being a superset, and explicitly documents edge-case behavior: closed/fully-booked returns empty channels with total_slots 0, while unknown store_id returns 404.

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?

The description is dense but every sentence earns its place: purpose, return fields, parameter nuance, and error behavior are each addressed in logical order. Nothing is redundant with the schema, and the critical scoping and edge-case information is front-loaded.

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?

Given only 2 parameters, no annotations, and no output schema, the description supplies all essential behavioral context: what fields come back, how grouping works, what fulfillment selects, how closed/full stores behave, and the 404 case. An agent can confidently call this tool without further inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds genuine value beyond the schema by clarifying that the fulfillment parameter is a separate, coarser vocabulary than the per-window service_type response field, preventing an agent from confusing the two enums.

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?

Opens with a clear verb+resource: 'List a Sonic Drive-In restaurant's order-ahead time slots.' It goes on to specify bookable windows grouped by service channel and local date, which cleanly distinguishes it from sibling tools like sonic_menu, sonic_store, and sonic_locations that cover other Sonic data.

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?

Provides clear context: the tool needs a store_id and optionally a fulfillment value, and explains what the returned data represents. However, it does not explicitly name alternatives or state when not to use this tool vs other Sonic endpoints, so it stops short of a 5.

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