Crawlora MCP

wingstop_menu

Read-only

Wingstop store priced menu: every category and listing (a standalone item, or a size/flavor family such as "6 pc Wing Combo" with one variant per size) with price, description and calorie range, for carryout or delivery.

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": {
      "path": "<path>"
    },
    "name": "wingstop_menu"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Required. Store path from a /wingstop/directory child with is_store true, or a /wingstop/store response's own path.
`service_mode`	No	One of: carryout, delivery. Defaults to carryout.

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

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds useful shape context (priced listings with per-size variants, calorie ranges), but says nothing about rate limits, auth, or persistence behavior beyond what annotations provide.

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?

One front-loaded sentence that immediately states resource and scope, with the parenthetical variant explanation earning its place. It is dense but the nested clarification makes it slightly harder to parse than an ideal definition.

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 need not be restated, and both parameters are fully described in the schema. The definition covers what is returned and the pricing/variant model, leaving only minor gaps around store-path prerequisites.

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 the required store path and the optional service_mode are already documented. The description's 'carryout or delivery' echoes the service_mode values without adding new syntax or defaulting detail, so it sits at the schema-driven 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?

Names a specific verb (fetch the priced menu), resource (Wingstop store menu), and scope, then clarifies structure — categories, standalone items vs. size/flavor families with one variant per size. This distinguishes it from siblings like wingstop_store, wingstop_directory, and wingstop_flavors.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The phrase 'for carryout or delivery' hints at the service_mode choice, but there is no explicit when-to-use guidance, no mention that a store path must be obtained from wingstop_directory first, and no routing against alternatives like wingstop_flavors or wingstop_delivery_store.

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?