Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

zaxbys_nearby

Find Zaxby's stores near a coordinate, sorted by distance. Returns address, phone, hours, open status, and fulfillment options.

Instructions

Find Zaxby's stores near a coordinate. Returns Zaxby's stores within a radius of a coordinate, nearest first: full address, phone, coordinates, current open status, per-channel hours (dine-in, drive-thru, carryout, pickup, delivery), and fulfillment/amenity flags. Each result's store_id pairs with GET /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

NameRequiredDescriptionDefault
limitNoMaximum stores to return, 1-50 (default 10)
radiusNoSearch radius in miles, 1-100 (default 25)
latitudeYesSearch center latitude
longitudeYesSearch center longitude

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the read-only nature (Find/Returns) and details the output content, including sorting (nearest first) and the cross-reference to the store endpoint. It does not mention side effects, auth, or rate limits, but for a search tool this is acceptable.

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 sentences with no fluff. The purpose is front-loaded, the return fields are listed compactly, and the cross-reference is a useful addition. Every word contributes.

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?

With no output schema, the description must explain the return structure, and it does thoroughly (fields, sorting, cross-reference). It also covers the default behavior implicitly via parameters. Nothing essential is missing for an agent to call and interpret this tool 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%, so parameters are already documented. The description adds minimal extra meaning: it reiterates the radius concept and mentions 'nearest first', which relates to sorting but not to parameter semantics. It does not go beyond the schema, so baseline 3 is appropriate.

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 clear verb-resource pair: 'Find Zaxby's stores near a coordinate.' It also enumerates the returned fields (address, phone, coordinates, open status, hours, flags), which distinguishes it from the menu or single-store sibling tools. The pairing note with /zaxbys/store further clarifies its scope.

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 description implies when to use it (find nearby stores) but does not explicitly state when to prefer a sibling like zaxbys_store or zaxbys_menu. It mentions the store_id pairing with the store endpoint, which hints at using that for a single record, but stops short of a clear when-to-use vs. alternative statement.

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