Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dominos_customization

Retrieve a Domino's store's build-your-own menu catalog with sizes, crusts, toppings, sides, option codes, dietary flags, and cooking instructions.

Instructions

Get one Domino's store's full build-your-own customization catalog. Returns one Domino's US store's full build-your-own customization catalog, grouped by product category (Domino's own names, e.g. "BuildYourOwnDomino" for pizza, "GSalad" for garden salads): every selectable size, crust/flavor style, topping, and side, each with its own code, name, description, dietary/placement flags (e.g. Meat, Vege, Sauce, WholeOnly), and any other attributes Domino's attaches (e.g. ExclusiveGroup for mutually-exclusive options). Also returns cooking instructions (bake level, cut style, seasoning), grouped. Store ids come from GET /dominos/store-locator. An unknown store id returns 404.

Input Schema

TableJSON 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/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and does well: it discloses that results are grouped by product category, enumerates the option fields (code, name, description, dietary/placement flags), mentions exclusive-group semantics, and covers cooking instructions. It omits auth/rate-limit behavior, but for a read-only catalog endpoint the disclosure is rich.

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?

Purpose is front-loaded in the first sentence, and the remaining detail about grouping, fields, flags, and errors is worth including given there is no output schema. It is a bit dense with parenthetical examples, but not padded or redundant in a harmful way.

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?

Since no output schema exists, the description must explain returns, and it does so thoroughly: category grouping, Domino's native category names, per-option attributes, mutually-exclusive grouping, and cooking instructions. It also covers the request-side prerequisite (store id source) and the failure mode (404).

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 coverage is 100% and the schema already documents store_id as coming from /dominos/store-locator, so the description largely repeats that. It adds marginal value by noting the 404 error behavior for an unknown store id. Baseline 3 is appropriate when the schema already does the heavy lifting.

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 build-your-own customization catalog) with clear scope. It is easily distinguishable from sibling tools like dominos_menu, dominos_nutrition, and dominos_store_locator because it explicitly scopes to build-your-own customization options rather than menus or nutrition.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It tells the agent where the store_id comes from (GET /dominos/store-locator) and that an unknown id returns 404, which is useful prerequisite context. However, it never states when to choose this tool over siblings like dominos_menu, and gives no explicit when/when-not guidance. Usage is implied rather than directed.

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