Skip to main content
Glama

One product in full

get_product
Read-onlyIdempotent

One product in full: photos, every option with its choices, and, for online stores, the variant for the chosen options with its id, price and stock. The variant id works with start_checkout.

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": {
      "business": "<business>",
      "id": "<id>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe product id from search_products.
optionsNoThe customer’s choices, e.g. {"Color": "Rose Gold", "Ring size": "12"}.
businessYesThe business id from find_businesses, e.g. "carat-story".

Output Schema

NameRequiredDescriptionDefault
productYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive operation, and the description adds genuinely new context: variant data is only produced for online stores, depends on the chosen options, and its id is consumable by start_checkout. It does not cover what happens when requested options don't match an available choice.

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?

A single dense sentence that front-loads the resource and enumerates returns in priority order, with the cross-tool pointer last. It is slightly run-on but every clause carries information.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile; the description still adds the conditional online-store variant behavior and the downstream start_checkout link. The main residual gap is error/edge behavior for unmatched options.

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%, with both id and business documented and the options example given inline, so the schema does the heavy lifting. The description adds the useful signal that the options parameter drives which variant is returned, which is meaning beyond the schema's field-level text.

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 names a specific resource and enumerates its contents (photos, options with choices, and the store variant with id, price and stock), which is far more than a restatement of the title. It implicitly separates itself from search_products by describing a single-product detail fetch, but never names that sibling explicitly.

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?

Usage is only implied through the workflow chain: the product id comes from search_products and the returned variant id feeds start_checkout. There is no explicit when-to-use or when-not statement, and no guidance on when the options parameter should be supplied versus omitted.

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