Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

popeyes_locations

Find nearby Popeyes restaurants by latitude and longitude, returning store IDs, addresses, phone numbers, amenities, and weekly hours. Filter by market and radius.

Instructions

Find Popeyes restaurants near a location. Returns Popeyes restaurants near a latitude/longitude. Each restaurant carries its internal id and numeric store id (the value /popeyes/menu takes), full address with coordinates, phone, the operating franchise group, amenity flags (breakfast, delivery, drive-thru, playground, takeout, wifi, halal, dark kitchen) and the full published week of hours for dining room, drive-thru, delivery and curbside separately. A coordinate with no nearby Popeyes returns an empty list rather than an error.

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

Input Schema

Name	Required	Description
`market`	No	Restaurant market: `US` (default) or `CA`
`radius`	No	Search radius in meters, 1-50000 (default 8000)
`latitude`	Yes	Search center latitude
`longitude`	Yes	Search center longitude
`max_results`	No	Maximum restaurants to return, 1-50 (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.16.2Sep 10, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the transparency burden, and it handles it well: it reveals the returned fields, the store id linkage to /popeyes/menu, and the empty-list instead of error edge case. It does not go further into ordering, sorting, or other edge cases, but it discloses the most decision-relevant behavior.

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 and the long middle sentence earns its place by itemizing amenities and return fields. The opening sentence is somewhat redundant with the second, which costs the perfect 5, but overall the prose is dense and useful.

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, so the description must explain what callers receive; it does this thoroughly, including ids, address, phone, franchise group, amenity flags, and detailed hours. It even includes the empty-list edge case and cross-links the store id to /popeyes/menu, making the description effectively complete for 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 the baseline is 3 and the description does not need to duplicate parameter documentation. The description reinforces 'near a latitude/longitude' and implies radius/distance behavior, but adds no parameter-level detail beyond the schema.

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 clearly names the action ('Find') and the resource ('Popeyes restaurants near a latitude/longitude'), so an agent can tell this is a nearby-location search tool. However, it does not explicitly contrast itself with the sibling tool popeyes_location, leaving the plural-vs-singular distinction to be inferred.

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 intended use is clear: call this when you need Popeyes restaurants near a coordinate, with latitude/longitude as the required basis. It does not mention when to prefer alternatives such as popeyes_location or popeyes_menu, so it falls just short of explicit sibling steering.

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

Deploy Server