Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

whataburger_sitemap

Retrieve Whataburger store URLs from its sitemap index. Filter by page kind (store, curbside, delivery, directory) and paginate to enumerate all entries.

Instructions

Browse Whataburger's store-URL index. Returns one page of Whataburger's sitemap-declared store index -- about 3,950 URLs at time of writing. Unlike some other store locators in this API, Whataburger publishes a single flat sitemap file rather than a sharded index. Each entry carries a kind: "store" is a restaurant's canonical detail page, "curbside" and "delivery" are separate pages Whataburger publishes for that same restaurant's curbside or delivery service, and "directory" is a state- or city-level listing page with no address of its own. Filter with kind to enumerate one page variant. A page past the end returns an empty list rather than an error, so a caller can walk to exhaustion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoFilter by page kind. One of store, curbside, delivery, directory. Default all.
pageNo1-based page (default 1)
page_sizeNoEntries per page, 1-500 (default 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / kind / enum
      Added value: +[
+  "store",
+  "curbside",
+  "delivery",
+  "directory"
+]
  2. Addedv1.16.2

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden, and it does so well: it explains the flat-sitemap structure, the meaning of each kind value, pagination semantics, and the empty-list behavior past the end. It does not explicitly state return-field formatting or safety characteristics, but the browse/index framing is clear and no contradictions 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 dense but tightly structured: every sentence contributes either scope, differentiation, kind semantics, filtering guidance, or pagination behavior. It front-loads the core purpose and does not waste words.

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 that this tool has no annotations and no output schema, the description is unusually complete: it defines the data source, entry kinds, practical page size context, and the sentinel behavior that lets a caller paginate to exhaustion. An agent has enough information to select, invoke, and iterate through this tool correctly.

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%, so the schema already documents the parameters, but the description adds meaningful value by explaining the semantic distinction among kind values and by describing page-exhaustion behavior. It maps the kind filter to use cases ('enumerate one page variant') beyond the enum labels.

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 opens with a specific verb and resource—'Browse Whataburger's store-URL index'—and clarifies it returns sitemap-declared store URLs, about 3,950 at time of writing. It distinguishes this tool from sharded store locators and defines the page variants, so an agent can tell it apart from related tools like whataburger_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?

The description gives clear context: it is a paginated, flat-sitemap index tool, and it explains how to filter by kind and walk through pages. It contrasts with 'some other store locators' but does not explicitly name sibling alternatives or state when this tool should be chosen over whataburger_store, so it stops short of full when/when-not 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