Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Remote

papajohns_india_menu

Get Papa John's India menu with live prices in INR, including categories, deals, dietary tags, and item availability. Filter by category, tag, or store to find current pricing and discounts.

Instructions

Get the Papa John's India priced menu (INR). Returns Papa John's India menu with live prices in Indian Rupees, from papajohns.in's own ordering backend. This is the India market only -- prices, items, and availability are India-specific and are not comparable to Papa John's US/Canada data (see GET /papajohns/nutrition for US national reference data). Returns every category with its items and deals: list price, strike-through price where a discount is active, dietary tags (Veg, Non Veg, Spicy), images, and the store/channel/day combinations where an item is blacked out. Set include_options=true to also get each item's full size, crust, topping, sauce, and drizzle tree with per-option prices -- this makes the response very large, so prefer GET /papajohns/india/menu/item for one item's options. Pricing is franchise-wide rather than per-store; store_id, channel_id, and day filter item availability, not price, and only take effect when all three are supplied.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayNoWeekday. One of: 0 (Sunday), 1 (Monday), 2 (Tuesday), 3 (Wednesday), 4 (Thursday), 5 (Friday), 6 (Saturday). Only applies together with store_id and channel_id.
tagNoReturn only items carrying this tag, e.g. Veg, Non Veg, Spicy. Case-insensitive.
store_idNoHide items blacked out at this store id (see GET /papajohns/india/stores). Only applies together with channel_id and day.
channel_idNoOrder channel. One of: 1 (Delivery), 2 (Take Away), 3 (Dine In), 4 (Drive Through Pickup). Only applies together with store_id and day.
category_idNoReturn only this category id
include_optionsNoInclude every item's full size/crust/topping option tree with prices. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A5/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden, and it delivers: live prices, franchise-wide rather than per-store pricing, blackout filtering semantics, and the size consequence of include_options. It also explains that filters affect availability, not price, which is important behavioral context beyond a simple menu fetch.

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?

Every sentence earns its place: market scope, source, return contents, alternative endpoints, and filter preconditions are all packed in without repetition. The core purpose is front-loaded, and the length is justified by the number of nontrivial behavioral caveats.

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 compensates by enumerating return contents: categories, items, deals, list/strike-through prices, dietary tags, images, and blackout combinations. It also covers when to prefer sibling endpoints and how parameters interact, so an agent has what it needs to invoke the tool correctly.

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

Parameters5/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, but the description adds significant meaning beyond the schema: include_options returns the full size/crust/topping tree and makes the response very large, and store_id/channel_id/day filter availability rather than price and only apply together. This materially helps an agent choose and set parameters correctly.

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 verb ('Get'), resource ('Papa John's India priced menu'), currency (INR), and source (papajohns.in backend). It explicitly scopes to India and contrasts with US/Canada data, and references GET /papajohns/india/menu/item for item-level options, clearly differentiating it from sibling menu endpoints.

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?

Names alternatives explicitly: GET /papajohns/nutrition for US national reference data, and GET /papajohns/india/menu/item when only one item's options are needed. It warns that include_options=true produces a very large response and gives the precondition that store_id, channel_id, and day only take effect when all three are supplied.

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