Crawlora MCP

wingstop_delivery_store

Read-only

Find the single Wingstop store that will deliver to an address, plus drive time. 404 if none delivers there.

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": {
      "address1": "<address1>",
      "city": "<city>",
      "state": "<state>",
      "postal_code": "<postal_code>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "wingstop_delivery_store"
  }
}

Input Schema

Name	Required	Description
`city`	Yes	Required. Delivery address city.
`state`	Yes	Required. Delivery address state (region), e.g. a two-letter code.
`address1`	Yes	Required. Delivery address line 1.
`latitude`	Yes	Required. Delivery address latitude.
`longitude`	Yes	Required. Delivery address longitude.
`postal_code`	Yes	Required. Delivery address postal code.
`country_code`	No	Optional. Delivery address country code. Defaults to US.

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

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real behavioral context beyond that: it returns exactly one store rather than a list, includes drive time, and returns 404 when nothing delivers. This failure-mode disclosure is genuinely useful and not inferable from the annotations.

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?

Two short sentences, zero filler, and the core capability (single delivering store) is front-loaded before the error condition. Every clause earns its place.

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?

With an output schema present and annotations covering the safety profile, the description needn't explain return values. It adequately covers purpose, the extra drive-time output, and the 404 behavior, though it omits any note on country defaulting or cross-tool selection.

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%, with all seven address parameters documented in the schema itself, so the baseline of 3 applies. The description only gestures at 'an address' without adding format or requiredness nuance beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (Find), resource (the single Wingstop store), and scope (that will deliver to an address), plus an extra output detail (drive time). It implicitly distinguishes itself from sibling list-style tools like wingstop_nearby by emphasizing a single store, but never names an alternative explicitly.

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?

It gives a clear use context - resolve the one store that delivers to a given address - and discloses the failure condition (404 if none delivers). It stops short of naming when to prefer wingstop_nearby or wingstop_store, so there is no explicit exclusion or alternative routing.

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?