Skip to main content
Glama

Catalog product

catalog_product

One product from the catalog by id, with its price, live stock and the exact steps to buy it. Ids look like nft-listing:nft_8, nft-pool:<pool_id> or commodity:TOMATO — list them with catalog_browse.

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

Input Schema

NameRequiredDescriptionDefault
idYesProduct id from catalog_browse, e.g. commodity:TOMATO

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does reasonably well: it discloses the return payload (price, live stock, and 'exact steps to buy'), which makes clear this tool informs a purchase rather than performing one — an important distinction given buy-oriented siblings. It does not state error behavior for malformed ids or how 'live' stock freshness is determined.

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?

Two tight sentences: the first front-loads what the tool returns, the second handles id format and the discovery alternative. Every clause carries information and nothing is padded.

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?

For a single-required-param read tool with no output schema, the description covers return contents, id sourcing, and id syntax well enough to invoke correctly. The only gap is failure behavior for ids that don't resolve.

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 already 100%, so baseline is 3, but the description adds real meaning by showing the id namespace patterns (nft-listing:nft_8, nft-pool:<pool_id>, commodity:TOMATO) beyond the single schema example. It still doesn't say whether unknown or malformed ids raise an error or return empty.

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+resource (fetch one product from the catalog by id) and enumerates what comes back: price, live stock, and purchase steps. It also names the id namespaces and the sibling (catalog_browse) that supplies them, so an agent can distinguish it from listing tools without opening the schema.

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?

The closing clause 'list them with catalog_browse' gives an explicit alternative for the discovery step and implies this tool is used once an id is in hand. There is no explicit when-not-to-use or error guidance (e.g., what happens with an unknown id), so it falls short of full routing guidance.

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