Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sonic_sitemap

Retrieve Sonic Drive-In's menu and store-locator sitemaps, listing page paths for menu categories, items, and store locations to use with item or store endpoints.

Instructions

Browse Sonic Drive-In's menu-page or store-locator sitemap. Returns one page of Sonic Drive-In's own sitemap: section=menu lists every menu category/subcategory/item page (298 pages), section=locations lists every store-directory page (state/city/store, ~3,365 stores). Each entry's path is what GET /sonic/item (menu section) or GET /sonic/store (locations section, kind=store) takes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoOptional. Filter by page kind. menu: index, category, subcategory, item. locations: index, state, city, store.
pageNoOptional. 1-based page, default 1.
sectionYesWhich sitemap to read
page_sizeNoOptional. Entries per page, 1-500, default 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / kind / enum
      Added value: +[
+  "index",
+  "category",
+  "subcategory",
+  "item",
+  "state",
+  "city",
+  "store"
+]
    • addedInput schema / properties / section / enum
      Added value: +[
+  "menu",
+  "locations"
+]
  2. Addedv1.16.2

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that it returns one page at a time, explains the pagination parameters (page, page_size implicitly), and states that entries contain paths used by other tools. It does not mention auth or rate limits, but for a read-only sitemap tool this is sufficient. No contradictions with annotations (none exist).

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 three sentences, front-loaded with the primary purpose, and includes useful specifics (page counts, path usage). It is efficient with no filler, making it easy for an agent to parse quickly.

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?

Given the schema covers all parameters and there is no output schema, the description gives a good sense of what to expect: sitemap entries with paths. It explains the relationship to other tools. It does not detail the exact structure of each entry beyond mentioning the path, but for a sitemap tool this is reasonably complete.

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 coverage is 100% (all parameters have descriptions), so baseline is 3. The description adds meaning for the 'section' parameter (explaining what menu vs locations yields) and for 'kind' (listing the allowed values for each section). It does not add anything beyond schema for 'page' and 'page_size', but the added context for the key parameters justifies a 4.

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?

The description clearly states the tool's purpose: browsing Sonic Drive-In's menu or store-locator sitemap. It specifies the two sections (menu, locations) and what each contains, with concrete counts (298 pages, ~3,365 stores). It also clarifies how the returned paths are used by other tools (GET /sonic/item and GET /sonic/store), effectively differentiating it from direct content tools.

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?

The description implies usage as a discovery/enumeration tool—it returns sitemap pages listing paths for other tools. It does not explicitly name alternatives or state when not to use it, but the context is clear: use this to get a list of menu pages or store pages. It lacks explicit exclusions but provides enough guidance.

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