Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

wendys_nearby

Locate Wendy's restaurants near a coordinate or address, returning nearest stores first with distance, hours, and order-availability details.

Instructions

Find Wendy's stores near a coordinate or address. Returns Wendy's stores within a radius of a search location, nearest first, via order.wendys.com's own restaurant-selector proximity search (the "Use Current Location" / "City, State, or Zipcode" flow at order.wendys.com's start-an-order screen) -- a materially richer, real-distance source than locations.wendys.com's classic-Yext locator (GET /wendys/directory, /wendys/store), which publishes no geosearch of its own. The search location is either a latitude/longitude pair or a free-text address query param (city/state, zip code, or full street address) that Wendy's own service geocodes server-side -- exactly one form is required; address takes priority if both are given. Each store carries its address, coordinates, phone, distance in miles, open/closed status, its published week of general and breakfast hours, and a few order-availability flags (breakfast, carry-out, mobile order, drive-thru, delivery, wifi) the ordering app itself uses to decide whether to offer the store for the current order type.

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	Maximum stores to return, 1-50, default 25
`radius`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.16.2Sep 10, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations, the description carries the full burden, and it delivers: it reveals the underlying source (order.wendys.com's restaurant-selector proximity search), the ordering (nearest first), the input exclusivity/priority rule, and the full returned store field set. No unclear behavioral traits remain that would surprise an agent.

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?

The description is front-loaded with the core purpose and every block of information serves a real need: differentiation, input rules, and return-value expectations. However, it is a single dense run-on paragraph with heavy parentheticals, so it could be better structured for scanning.

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?

There is no output schema and no annotations, so the description must explain both inputs and return values; it does both thoroughly. It specifies result fields, ordering, distance unit, input alternatives, priority, and defaults are already in the schema. Nothing essential for correct invocation or result interpretation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value beyond the schema by clarifying that exactly one search form is required, that address takes priority when both forms are given, and that addresses are geocoded server-side by Wendy's own service. These are genuine semantic enhancements over the property descriptions.

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?

The opening sentence states a specific verb, resource, and scope: 'Find Wendy's stores near a coordinate or address.' It further distinguishes itself from wendys_directory and wendys_store by noting they publish no geosearch, making the tool's unique role clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly contrasts this tool with the classic-Yext locator endpoints (GET /wendys/directory, /wendys/store), explaining they lack geosearch. This tells an agent when to prefer wendys_nearby instead of those siblings. It also clarifies the required input form: exactly one of address or lat/long, with address taking priority if both are supplied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server