Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dominos_menu

Retrieves a Domino's store's full structured menu by store id, returning categorized items with codes, descriptions, and priced size variants for building order or price-comparison apps.

Instructions

Get one Domino's store's full structured menu. Returns one Domino's US store's full menu, as a flat list of categories (each with a stable code/name path, e.g. "Pizza > Specialty Pizzas") and their items. Each item carries its code, name, description, and product type, plus every purchasable variant (size/style) with its own code, name, and price. Store ids come from GET /dominos/store-locator. An unknown store id returns 404.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "store_id": "<store_id>"
    },
    "name": "dominos_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
store_idYesDomino's store id, from /dominos/store-locator

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.2/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 full burden, and it delivers: it discloses the return shape (flat category list with code/name paths), item fields, per-variant pricing, and the error behavior ('An unknown store id returns 404'). It does not address auth or rate limits, but for a read-only menu fetch the 404 disclosure is the material behavioral fact.

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?

Front-loaded with purpose, then progressively deeper detail on categories, items, variants, and error handling; every sentence carries information. The opening 'Get...' and 'Returns...' sentences overlap slightly, costing a little efficiency.

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 one required parameter and no output schema, the description fully compensates by describing the return structure (categories, items, variants with prices), the id source, and the failure mode. Nothing an agent needs to call it correctly is missing.

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 store_id parameter is already documented in the schema. The description's note that ids come from store-locator restates what the schema param description says, so it adds no meaning beyond the structured field. Baseline 3 applies.

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') and resource ('one Domino's store's full structured menu'), and the US/store-scoped framing clearly distinguishes it from siblings like dominos_coupons, dominos_nutrition, and dominos_store_locator. An agent can select it without opening any schema.

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?

Explicitly routes the agent to the sibling that produces the input ('Store ids come from GET /dominos/store-locator'), which is genuine usage guidance. However, it gives no when-not guidance or comparison against the other dominos_* menu/coupon tools.

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