Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

sonic_locations

List Sonic Drive-In restaurants with ready-made store paths, filter by state or city, and page through sorted results.

Instructions

List Sonic Drive-In restaurants with ready-made store paths. Returns Sonic Drive-In's restaurant listing one page at a time, each entry already split into its country, state, city and address parts plus a ready-made path value that GET /sonic/store takes -- so enumerating restaurants needs no path parsing. Filter by state and/or city to narrow the list; city slugs come from GET /sonic/directory. Results are sorted by path so paging is reproducible. This listing covers more store pages than GET /sonic/directory counts, since the directory counts listed restaurants while this enumerates every published store page; a filter that matches nothing returns an empty locations array with total 0, not an error. If Sonic's live store-locator service refuses the request, the list is built from Sonic's public store sitemap instead (same entry shape; it can omit stores without a published page, and source_url shows which source answered).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity slug to filter by, from /sonic/directory
pageNo1-based page number. Defaults to 1.
stateNoTwo-letter state or province code to filter by
page_sizeNoEntries per page, 1-500. Defaults to 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations present, the description carries the full burden and delivers: results sorted by path for reproducible paging, pagination semantics, coverage exceeding the directory count, empty-filter returns an empty array with total 0 rather than an error, and a sitemap fallback when the live locator refuses, with source_url indicating the source.

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-loads purpose and the ready-made path benefit, then proceeds to filtering and edge cases. Information-dense but somewhat long; every sentence contributes meaning, though the fallback explanation could be tightened.

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 no output schema and no annotations, the description covers entry shape, source indication, pagination, empty-result behavior, and the fallback data source, which is everything an agent needs to call and interpret this tool 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 coverage is 100%, so the schema already documents city, page, state, and page_size. The description reiterates state/city filtering and the city-slug source, adding little beyond what the schema provides, so baseline 3 applies.

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 ('List Sonic Drive-In restaurants with ready-made store paths') and immediately frames the shape of each entry. It is clearly distinguishable from siblings like sonic_directory, sonic_nearby, and sonic_store.

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?

Tells the agent to filter by state/city and where city slugs come from (GET /sonic/directory), and explains that the ready-made path feeds GET /sonic/store. It gives clear context but does not explicitly state when to prefer this tool over sonic_directory or sonic_nearby.

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