Crawlora MCP

zaxbys_nearby

Read-only

Zaxby's stores near a coordinate, nearest first: full address, phone, coordinates, open status, per-channel hours, and fulfillment/amenity flags, read directly and anonymously from Zaxby's own backend. Each result's store_id pairs with zaxbys_store for the same record on its own.

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": "zaxbys_nearby"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Optional. Maximum stores to return, 1-50, default 10.
`radius`	No	Optional. Search radius in miles, 1-100, default 25.
`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 7, 2026

TDQS

A4.1/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. The description adds real value beyond them: it discloses the data provenance ('read directly and anonymously from Zaxby's own backend'), confirming no auth is needed, and specifies the ordering ('nearest first') and the exact fields returned.

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?

Purpose and ordering are front-loaded, and both sentences carry information (the field inventory and the sibling cross-reference). The long middle field list is dense but each item is substantive rather than filler.

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 available, the return-value inventory in the description is a helpful preview rather than a requirement, and the readOnly/openWorld annotations cover the safety profile. The cross-reference to zaxbys_store closes the main integration gap, leaving little missing for correct invocation.

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 latitude, longitude, limit and radius are already documented with ranges and defaults. The description only implies coordinate-based proximity and adds no syntax or format detail beyond the schema, making the baseline 3 correct.

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?

States a specific verb and resource ('Zaxby's stores near a coordinate, nearest first') and enumerates exactly what each result contains, so the agent knows what it gets without opening the output schema. It is clearly differentiated from the sibling zaxbys_store by framing this as a proximity search and the sibling as the single-record lookup.

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 second sentence explains the relationship to the alternative ('Each result's store_id pairs with zaxbys_store for the same record'), implying the drill-down pattern. It gives clear context but no explicit when-not or exclusions, so it stops short of full routing guidance.

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.