Skip to main content
Glama

Product popularity, history and prices

get_product
Read-onlyIdempotent

One product: its rank and share in each category it appears in, 12-month share history, and prices by region with shop links. Accepts an id or a name.

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

Input Schema

NameRequiredDescriptionDefault
regionNoPrice region: US, UK, EU, AU. Omit for all.
productYesProduct id or name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine value beyond that by disclosing the response content shape (per-category rank and share, 12-month history, regional prices with shop links), which matters because no output schema exists.

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?

A single sentence that front-loads the scope ("One product") and then enumerates the payload contents in one pass. No filler, no repetition of the title.

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 carries the burden of telling the agent what it gets back, and it does so concretely. The main remaining gap for a tool sitting among seven siblings is routing guidance, but nothing needed to invoke 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 coverage is 100% and the schema already says "Product id or name" and lists the region values US, UK, EU, AU with "Omit for all." The description's "Accepts an id or a name" and "prices by region" restate rather than extend the schema, so the baseline 3 applies.

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?

"One product: its rank and share in each category it appears in, 12-month share history, and prices by region with shop links" states a specific resource and enumerates exactly what comes back, so an agent knows this is a single-product deep-dive rather than a list or comparison. It does not name any sibling tool, so the differentiation from get_ranking or compare_products 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 Guidelines3/5

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

"One product" implies the single-record use case, and "Accepts an id or a name" clarifies input flexibility, but there is no when-to-use/when-not guidance. With siblings like search_products, compare_products, and best_in_category present, the agent is left to guess whether to search first to obtain an id or call this directly.

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