Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

papajohns_india_stores

List Papa John's India restaurants with addresses, phones, coordinates, and weekly hours per order channel. Get store IDs to filter the India menu.

Instructions

List Papa John's India restaurants. Returns every Papa John's India restaurant with its address, phone, coordinates, and weekly opening hours broken down per order channel (delivery, take away, dine in, drive-through pickup). These store ids are what GET /papajohns/india/menu's store_id availability filter is keyed on. India market only -- for US/Canada stores use GET /papajohns/directory, GET /papajohns/store, or GET /papajohns/nearby.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idNoReturn only hours for this order channel. One of: 1 (Delivery), 2 (Take Away), 3 (Dine In), 4 (Drive Through Pickup).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / channel_id / enum
      Added value: +[
+  "1",
+  "2",
+  "3",
+  "4"
+]
  2. Addedv1.16.2

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It clearly states what the tool returns: address, phone, coordinates, and weekly opening hours per order channel. It also indicates the response is a complete list ('every... restaurant'). It does not mention pagination or rate limits, but for a simple read-only list tool the output description is strong.

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 three sentences with no filler. The core purpose is front-loaded, return contents are summarized compactly, and the market/alternative guidance is placed at the end without redundancy.

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?

For a simple list tool with one optional parameter and no output schema, the description is complete: it states the resource, scope, return fields, and relationship to a related menu endpoint. The optional channel_id behavior is fully covered by the schema, so nothing critical is missing for an agent to invoke this correctly.

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%, and the single optional channel_id parameter already has a clear enum with human-readable labels for each channel. The description adds no additional parameter semantics, but the schema fully documents the parameter, so the baseline of 3 is appropriate.

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 opens with a specific verb and resource: 'List Papa John's India restaurants.' It clearly states the market scope ('India market only') and explicitly contrasts with US/Canada alternatives, making it easy to distinguish from sibling tools like papajohns_directory, papajohns_store, and papajohns_nearby.

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?

The description gives explicit usage boundaries: 'India market only' and names the exact endpoints to use for US/Canada stores. It also explains how the returned store IDs relate to GET /papajohns/india/menu's store_id filter, giving the agent concrete context for when this tool is relevant.

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