Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

papajohns_intl_product

Retrieve a single Papa John's product catalog record for international markets, including description, imagery, dietary markers, and customization rules. Use with the menu endpoint to get product IDs and pricing.

Instructions

Get one Papa John's product (international). Returns one product's own catalog record in one of six international markets: Chile, Costa Rica, Guatemala, Panama, Portugal, and Spain -- its description, imagery, dietary markers, and customization rules (whether toppings may be changed, how many extra ingredients are included free, and whether it can be used as one half of a half-and-half pizza). This record carries no price, because pricing is per restaurant: use GET /papajohns/intl/menu for prices. Product ids come from that same endpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketYesMarket. One of: chile, costa-rica, guatemala, panama, portugal, spain
product_idYesProduct id from GET /papajohns/intl/menu

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / market / enum
      Added value: +[
+  "chile",
+  "costa-rica",
+  "guatemala",
+  "panama",
+  "portugal",
+  "spain"
+]
  2. Addedv1.16.2

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that the record has no price and points to the menu endpoint for pricing, and it lists the contents of the record. However, it does not explicitly mention read-only status, error handling, or response format, which are minor gaps for a simple GET operation.

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 concise, consisting of three sentences that each add value. It front-loads the core purpose, then clarifies pricing and ID sourcing without redundancy or fluff.

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 simple two-parameter GET, the description covers what the record contains, what it omits (price), and where to obtain product IDs. It is sufficient for an agent to invoke it correctly, and the absence of an output schema is mitigated by the detailed field listing.

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 schema already documents both parameters. The description adds context by explaining that product_id comes from the menu endpoint and that the record excludes pricing, which slightly enriches understanding but does not substantially exceed what the schema provides.

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 clearly states the verb 'Get', the resource 'Papa John's product (international)', and the specific scope of six markets. It enumerates the returned fields (description, imagery, dietary markers, customization rules) and explicitly distinguishes itself from the pricing menu, making its purpose unambiguous and distinct from sibling tools like papajohns_intl_menu.

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 description explicitly instructs users to consult GET /papajohns/intl/menu for pricing, and notes that product IDs come from that same endpoint. This provides clear routing for when to use this tool versus the menu tool. It does not explicitly enumerate all alternative tools, but the guidance for the most relevant alternative is present.

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