Skip to main content
Glama

Configure product

product_configure
Read-only

Get all variants, option ids and allergens for configuring a product before adding it to cart.

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": {
      "productId": "<productId>",
      "deliveryType": "<deliveryType>"
    },
    "name": "product_configure"
  }
}

Input Schema

NameRequiredDescriptionDefault
productIdYesProduct id from menu_list.
deliveryTypeYesSelected delivery type. Delivery type affects product price.

Output Schema

NameRequiredDescriptionDefault
productNo
storeIdNo
deliveryTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / product / properties / allergens / items / properties / code
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description adds useful context about the returned data shape (variants, option ids, allergens), but says nothing about price sensitivity tied to delivery type or failure behavior for invalid/unavailable products. Modest added value on top of the annotations.

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?

A single front-loaded sentence that packs the returned fields and the workflow trigger with no filler. Nothing is redundant and the key information appears first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and full schema coverage, the description needn't explain return values, and it correctly focuses on purpose and workflow placement. The main residual gap is whether this call is mandatory before cart_add_item and how delivery-type-dependent pricing is surfaced.

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 both parameters are documented, including the enum values for deliveryType and the note that it affects price. The description contributes no additional meaning about how productId or deliveryType influence the returned variants or allergens, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Get') and enumerates the concrete payload: variants, option ids and allergens for a product. This is clearly distinguishable from menu_list (discovery) and cart_add_item (mutation). It stops short of a one-line statement of what the tool fundamentally is, but the resource and returned fields are unambiguous.

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?

The phrase 'before adding it to cart' gives an implied workflow position, effectively pointing at cart_add_item as the follow-up step. However, no alternative tool is named explicitly and there is no guidance on when this is unnecessary or what to do if configuration data is missing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources