Skip to main content
Glama

products_show

Read-onlyIdempotent

Options, defaults, quantities and file requirements for one product.

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": {
      "product": "<product>"
    },
    "name": "products_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
qtyNoCheck a quantity against what the printer offers (needs a region, or a size that implies one).
foldNoFilter by fold.
sizeNoFilter by size.
sidesNoFilter by sides.
stockNoFilter by stock.
finishNoFilter by finish.
optionNoFilter by any option, as key=value. Repeatable.
regionNoOnly this region's options, quantities and file rules: US or HK.
productYesProduct id or alias, e.g. flyer or brochure.
orientationNoFilter by orientation.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo
summaryNo
warningsNo
next_actionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is fully covered. The description adds only that the payload covers options, defaults, quantities and file requirements; the output schema carries the return shape, so this is modest added value rather than rich behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single tight sentence with no filler and the 'one product' scope is front-loaded. However, for a 10-parameter tool this level of terseness is under-specification rather than effective conciseness.

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

Completeness3/5

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

Rich structured data (full schema coverage, output schema, complete annotations) compensates for much of the gap, so an agent can still call it correctly. Still, a 10-param filtering tool whose description never explains how the filters combine or that qty requires a region falls short of fully self-explanatory.

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% with 10 documented parameters, so baseline is 3. The description's mention of 'options' and 'quantities' loosely echoes the option and qty parameters but adds no filtering syntax, region semantics, or repeatability detail beyond what the schema already states.

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

Purpose3/5

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

The phrase names the resource ('one product') and the kind of data returned (options, defaults, quantities, file requirements), which distinguishes it from products_list by scope. But it is a noun fragment with no verb, leaving the agent to infer that this is a read/lookup operation rather than a computation or validation.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites (e.g., needing a region for quantity checks), and no reference to alternatives such as products_list for browsing products. The agent must infer usage from the name and schema alone.

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