Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

papajohns_intl_stores

Find Papa John's restaurants in Chile, Costa Rica, Guatemala, Panama, Portugal, or Spain. Search by coordinates or lookup by ID, getting full store details like hours, payments, and delivery zones.

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. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / fulfillment / enum
      Added value: +[
+  "delivery",
+  "pickup"
+]
    • addedInput schema / properties / market / enum
      Added value: +[
+  "chile",
+  "costa-rica",
+  "guatemala",
+  "panama",
+  "portugal",
+  "spain"
+]
  2. Addedv1.16.2

TDQS

A4.9/5.0
Behavior5/5

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

Even without annotations, the description thoroughly discloses behavior: what fields each restaurant carries (address, coordinates, phone, hours, payment methods, delivery zones, live open flags), ranking by distance, default pagination of five, page/limit behavior including when they are ignored, and the meaning of the returned id and menu_id in relation to other endpoints. It also notes there is no radius limit and that total_count reflects the market's whole restaurant count.

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?

The description is dense but well-organized, front-loading the core purpose and market scope before detailing response contents, pagination, id semantics, and alternatives. Every sentence carries useful information; there is no redundancy or filler.

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?

Despite having no output schema, the description fully covers what an agent needs: return data scope, ranking and pagination behavior, the two call patterns, and the relationship to related endpoints. The only minor omission is an explicit 'read-only' statement, but the tool's nature as a store locator makes that implicit. Overall it is complete for a tool of this complexity.

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% and the schema already documents parameters and their constraints. The description adds meaning beyond the schema by stating the default page size (five), the two mutually exclusive lookup modes (coordinate vs. store_id), and that fulfillment/coordinates are used only in the search case. It does not restate every schema field but supplements it with usage-level semantics.

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 description states a specific verb and resource ('Find Papa John's restaurants in an international market') and enumerates the exact six markets it covers. It also names sibling tools for other regions (India, US/Canada), clearly differentiating itself from similar store-finding tools in the family.

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?

Provides explicit when-to-use and when-not-to-use guidance: it covers six named markets only, and directs users to GET /papajohns/india/stores for India and GET /papajohns/directory, /papajohns/store, or /papajohns/nearby for US/Canada. It also distinguishes between the two invocation modes (coordinate search vs. store_id lookup) and the delivery/pickup fulfillment options.

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