Crawlora MCP

wendys_nearby

Read-only

Wendy's proximity store search: stores within a radius of a lat/long, nearest first, with distance, address, hours-derived open status and order-availability flags (breakfast, carry-out, mobile order, drive-thru, delivery, wifi).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wendys_nearby"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Optional. Maximum stores to return, 1-50, default 25.
`radius`	No	Optional. Search radius in miles, 1-100, default 20.
`address`	No	Free-text city/state, zip code, or street address to search near. An alternative to latitude/longitude -- required unless both of those are given.
`latitude`	No	Search center latitude. Required unless address is given.
`longitude`	No	Search center longitude. Required unless address is given.

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.8/5.0

Behavior4/5

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

Annotations already cover readOnly and openWorld safety, so the bar is lower. The description adds genuinely useful context beyond them: results are ordered nearest-first, and each store carries distance, address, hours-derived open status and order-availability flags. It stops short of noting limits/pagination behavior.

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?

A single, densely informative sentence that front-loads the tool's identity and ordering semantics before listing the returned fields. No 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?

For a proximity-search tool with an output schema, the definition is essentially complete — it conveys input model, ordering, and returned fields. Only minor gaps (limit/radius defaults are in the schema, pagination behavior) remain, and those are schema-covered.

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 coverage is 100%, so the schema fully documents limit, radius, address, latitude and longitude. The description only restates the lat/long-plus-radius input model without adding syntax, format, or default details, so baseline 3 applies.

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?

States a specific verb+resource ('proximity store search') with clear scope: stores within a radius of a lat/long, nearest first. This implicitly separates it from wendys_directory (browse) and wendys_store (single store), though it 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 only implied — the agent infers you call this when you need stores near a location. There is no explicit when-to-use guidance and no mention of the alternative siblings (wendys_directory, wendys_store) to route between them.

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?