Crawlora MCP

wingstop_nearby

Read-only

Wingstop stores within a radius of a coordinate, sorted nearest first, with address, phone, general hours and fulfillment channels per store; each result's slug can be passed directly to wingstop_menu.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "wingstop_nearby"
  }
}

Input Schema

Name	Required	Description
`radius`	No	Optional. Search radius in miles, 1-100, default 20.
`latitude`	Yes	Required. Search center latitude.
`longitude`	Yes	Required. Search center longitude.

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

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral value beyond that: result ordering (nearest first), the exact per-store fields returned (address, phone, general hours, fulfillment channels), and the slug-to-wingstop_menu handoff.

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?

A single dense sentence that front-loads the core behavior (nearby stores sorted by distance) and appends the payload fields and the slug handoff. Every clause carries information, though the return-field enumeration slightly overlaps with the existing output schema.

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, the description need not detail return values, yet it gives an accurate preview of the per-store fields and the chaining path to wingstop_menu. Combined with 100% schema coverage and clear annotations, an agent has essentially everything needed to call it 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 description coverage is 100% – latitude, longitude, and radius with its 1-100 mile range and default 20 are all documented in the schema. The description restates the coordinate/radius concept but adds no syntax, units, or edge-case detail beyond what the schema already supplies.

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 names the specific resource (Wingstop stores), the operation (find within a radius of a coordinate), and the ordering (sorted nearest first). It implicitly separates itself from wingstop_directory (full directory) and wingstop_store (single store) via the radius/coordinate framing, but never names those siblings explicitly.

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?

Usage is implied: use it when you have a coordinate and want a local set of stores. The downstream routing to wingstop_menu via slug is helpful, but there is no statement of when to prefer this over wingstop_directory or wingstop_store, and no exclusion criteria.

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?