Skip to main content
Glama

Read a product with evidence

get_product
Read-onlyIdempotent

Use this to answer "does product X have/support Y" and for the full profile of one product: every documented attribute with verification_state, confidence, observed_on and source URLs; scoped values (one edition, region or package only), withdrawn statements, register identifiers and the vendor mark. Needs the slug from search_products. Prices are at /api/v1/products/{slug}/prices. An attribute with verification_state "unknown" was searched and not found - say so, and never report it as the product lacking the feature.

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

Input Schema

NameRequiredDescriptionDefault
slugYesThe product slug from search_products, e.g. "apple-macbook-air".
attributesNo"all" returns every attribute including the unknown ones; "documented" omits the unknown ones and counts them instead. Use "documented" to save context when the gaps do not matter.all

Output Schema

NameRequiredDescriptionDefault
urlYes
kindYes
nameYes
slugYes
statesYes
vendorYes
contractYes
coverageYes
withdrawnYes
attributesYes
identifiersYes
scoped_attributesYes
unknown_attributes_omittedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context the annotations cannot carry: the meaning of verification_state "unknown" (searched and not found) and how to report it, plus the distinction between scoped values and withdrawn statements. That is the kind of interpretive guidance an agent needs to avoid a wrong answer.

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 and the return contents are front-loaded, followed by the precondition, the alternate endpoint, and the interpretation rule. It is dense but nearly every clause carries operational meaning; the long attribute enumeration sentence is slightly heavy but not wasteful.

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?

An output schema exists, so return structure need not be explained in prose, and the description still covers inputs' origin, scope of returned data, and interpretation rules for gaps. For a two-parameter read tool, nothing an agent needs to call it correctly is missing.

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 there, including the enum semantics of "documented" vs "all". The description only reinforces the slug's provenance (from search_products), which is a small addition beyond the schema, so the baseline 3 is appropriate.

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 concrete verb and resource — the full profile of one product, including documented attributes with verification_state, confidence, observed_on and source URLs, scoped values, withdrawn statements, register identifiers and the vendor mark. It also names the specific question it answers ("does product X have/support Y") and routes prices to a different endpoint, so an agent can distinguish it from search_products and get_product_record.

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

Usage Guidelines5/5

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

Gives explicit when-to-use framing (support questions, single-product profile) and an explicit when-not/precondition: the slug must come from search_products, and prices live at /api/v1/products/{slug}/prices. It also states a downstream behavioral rule — never report an "unknown" attribute as the product lacking the feature.

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