Skip to main content
Glama

AgentShopping

get_product

Fetch one product by slug, gtin or id, with ranked offers, coupons, price history and JSON-LD. Sample rows are labelled sample=true.

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
idNo
gtinNo
langNo
slugNo
countryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose the payload shape (ranked offers, coupons, price history, JSON-LD) plus a genuinely useful data caveat that sample rows are labelled sample=true. It omits error behavior when an identifier is not found, whether any authentication or rate limits apply, and which identifier takes precedence when several are supplied.

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 compact sentences, front-loaded with the core action and followed by the returned payload and the sample-data caveat. No filler or repetition.

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?

With no output schema and no annotations, the description does well to enumerate the returned sections and the sample flag, but it is thin for a five-parameter tool with zero schema coverage. Identifier precedence, the lang/country effect on localized results, and not-found behavior are all unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, so the description must compensate and largely does not: it names slug, gtin and id but says nothing about lang (the only enum) or country, nor which identifier wins if multiple are passed, nor expected formats such as GTIN length.

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 gives a specific verb plus resource ('Fetch one product') and names three lookup keys, so it is clearly a single-item retrieval rather than a listing. It does not differentiate itself from siblings like search_offers or list_coupons, even though it embeds coupon and offer data, leaving mild ambiguity about when the aggregate view is preferable.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The only usage-relevant detail is the identifiers it accepts, which is parameter semantics rather than guidance on selecting this tool over search_offers or list_coupons.

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