Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

dominos_nutrition

Get live calorie counts for a Domino's product by store and product code, including custom build-your-own pizzas with size, base, and toppings. Returns accurate Cal-O-Meter data for one configuration per call.

Instructions

Get calorie information for one Domino's product configuration. Returns calorie information (Domino's own "Cal-O-Meter" data) for one product at one store. For a named/fixed menu item (a specialty pizza, bread, wing, pasta, sandwich, salad, drink, or dessert -- any item code from GET /dominos/menu), give only store_id and product_code; the item's default configuration is used. For a build-your-own pizza, also give size, base, and any topping codes -- calories are computed for that exact configuration, matching Domino's own live calculator. size and base must be given together; toppings requires both. Reads live, not from a cache -- each call creates and discards one anonymous cart server-side, so it is slower than this family's other endpoints. An unknown product code, or an invalid size/base/topping combination, returns an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseNoBuild-your-own crust code. Required together with size.
sizeNoBuild-your-own size code, from /dominos/menu's variants. Required together with base.
store_idYesDomino's store id, from /dominos/store-locator
toppingsNoRepeatable. Topping codes to add to a build-your-own pizza. Only used together with size+base.
product_codeYesA product code from /dominos/menu's items[].code -- a named/fixed item, or a build-your-own base (e.g. S_PIZZA)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / toppings / items
      Added value: +{
      +  "type": "string"
      +}
  2. Addedv1.16.2

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so excellently. It discloses that reads are live, each call creates and discards an anonymous cart server-side, performance is slower, unknown codes or invalid combinations error, and fixed items use default configurations while BYO calories are computed exactly.

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?

Dense but efficient; every sentence contributes essential information. The main purpose is front-loaded, followed by logical mode-based usage, dependencies, performance caveat, and error behavior, with no 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?

Given moderate complexity and no output schema, the description is highly complete: it covers return type, both invocation modes, required and optional parameter relationships, data provenance, performance behavior, and error conditions. Little is left for the agent to infer.

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 already documents parameter dependencies. The description adds value beyond the schema by explaining the two usage modes, clarifying that fixed-item calls should include only store_id and product_code, and noting that calories match Domino's live calculator.

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?

Opens with a specific verb and resource: 'Get calorie information for one Domino's product configuration.' It clearly distinguishes itself from sibling tools like dominos_menu and dominos_coupons by scoping to calorie lookup for one configuration at one store, and references its Cal-O-Meter data source.

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?

Provides explicit parameter-selection guidance for two distinct cases: fixed menu items (store_id + product_code only) and build-your-own pizzas (size, base, toppings). It notes the live, uncached behavior and that it is slower than 'this family's other endpoints', giving a clear performance-based consideration, though it does not name a specific alternative tool for menu retrieval.

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