Skip to main content
Glama

Get a product and its certification evidence

get_product
Read-onlyIdempotent

Get one published product by slug or ASIN, with every claim shown honestly (including lapsed, unverifiable and stale ones) and the history of reads behind each claim. Give exactly one of slug or asin. Link people to the url given in each result and never construct a retailer link. Say "last read on " for a certification. Say "brand-level" when evidence_scope is "brand". Ratings are scores, not certifications.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
asinNo
slugNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, and the description adds real substance on top: results include lapsed, unverifiable and stale claims plus the read history behind each claim. That is meaningful disclosure about what the response contains, though it says nothing about size, pagination, or failure modes for an unknown slug/ASIN.

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 is front-loaded in the first clause, followed by a compact set of operating rules. A few sentences are presentation conventions ('Ratings are scores, not certifications') that read as list items rather than prose, but each still earns its place by preventing a specific misinterpretation.

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 no output schema, the description must convey return content, and it does: per-claim evidence, read history, evidence_scope, and a url to link. For a two-parameter read tool this is close to sufficient, with only error handling and result volume left unstated.

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 description coverage is 0% and both parameters are optional with no oneOf constraint, so the description carries the burden — and it does, stating 'Give exactly one of slug or asin', which supplies the mutual-exclusivity rule the schema omits. It does not describe identifier formats (e.g., ASIN shape or slug syntax), leaving a minor gap.

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 opening clause gives a specific verb and resource ('Get one published product by slug or ASIN') and scopes it to a single published product, which implicitly separates it from a bulk search. It stops short of naming a sibling such as search_products as the discovery path, so differentiation is inferred rather than stated.

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?

It gives concrete operational rules: supply exactly one of slug or asin, link to the returned url and never build a retailer link, and how to phrase 'last read on <date>' and 'brand-level'. What is missing is routing guidance — nothing says to use search_products first when the identifier is unknown.

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