Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Remote

papajohns_intl_stores

Find Papa John's restaurants in Chile, Costa Rica, Guatemala, Panama, Portugal, or Spain by location or store ID. Get addresses, hours, payment methods, delivery zones, and open status in ranked JSON.

Instructions

Find Papa John's restaurants in an international market. Returns Papa John's restaurants in one of six international markets: Chile, Costa Rica, Guatemala, Panama, Portugal, and Spain -- either every restaurant near a coordinate, or one known restaurant looked up by id. Each restaurant carries its address, coordinates, phone, per-weekday opening hours split by fulfillment channel, accepted payment methods, delivery zones with their minimum-order and free-delivery thresholds, and live delivery/pickup open flags. Restaurants come back ranked by distance with no radius limit, five at a time by default; page and limit walk the rest, and the response reports total_count, the market's whole restaurant total. The returned id is what GET /papajohns/intl/menu prices against, and menu_id is what GET /papajohns/intl/ingredients reads. This covers those six markets only -- for India use GET /papajohns/india/stores, and for the US and Canada use GET /papajohns/directory, GET /papajohns/store, or GET /papajohns/nearby.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoOne-based page of the distance-ranked restaurants. Ignored for a store_id lookup and for pickup, neither of which is paginated.
limitNoRestaurants per page, 1-100. Ignored for a store_id lookup and for pickup, neither of which is paginated.
marketYesMarket. One of: chile, costa-rica, guatemala, panama, portugal, spain
latitudeNoLatitude to search around. Required unless store_id is supplied.
store_idNoLook up one known restaurant by id instead of searching a coordinate. Supply either store_id, or both latitude and longitude.
longitudeNoLongitude to search around. Required unless store_id is supplied.
fulfillmentNoOne of: delivery (default, every nearby restaurant), pickup (only restaurants accepting pickup orders). Ignored when store_id is supplied.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are present, so the description carries the full burden. It discloses pagination defaults (five at a time, page/limit), distance ranking with no radius limit, response total_count, per-store fields including hours, fulfillment channel, payment methods, delivery zones, and live open flags, plus cases where page/limit are ignored.

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?

Although long, the description is dense and front-loaded with the key purpose before enumerating output fields and routing. No sentence is filler; the length is warranted by seven parameters and no output schema.

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 enumerates the important returned data (address, coordinates, phone, weekday hours by channel, payment methods, delivery zones, live flags, total_count). It covers both input modes, pagination edge cases, and cross-references to sibling endpoints, leaving no major gap for a store lookup tool.

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 complementary semantics: it clarifies coordinate-vs-store_id search modes, states that fulfillment filters delivery versus pickup, and notes pagination is ignored for store_id and pickup lookups. It also links returned id and menu_id to downstream menu/ingredients tools.

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 action ('Find Papa John's restaurants'), the resource (international stores), the six eligible markets, and the two lookup modes (coordinate search or store_id). It differentiates from sibling store tools by declaring geographic scope and naming alternatives.

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?

Explicitly says when to use this endpoint (six international markets) and routes to siblings: India via GET /papajohns/india/stores, US/Canada via /directory, /store, /nearby. It also identifies downstream menu/ingredients endpoints based on returned ids, reducing ambiguity about which papajohns tool to call next.

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

Install Server

Other Tools