Skip to main content
Glama

Ask Bestie Computers

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, CA, UK, EU, SE, NO, DK, AU. Omit for all.
productYesProduct id or name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds the useful disclosure that results include shop links and are scoped per category the product appears in — a non-obvious behavior — but says nothing about auth, rate limits, or what happens for an unknown id/name.

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?

Two tight sentences, front-loaded with the resource and its payload, ending with the input constraint. Nothing is filler, though the payload list is dense enough that light structuring (e.g. separating return fields from input notes) would aid scanning.

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 return-value burden and does so by enumerating rank, share, history window, and regional pricing with links. For a 2-parameter read tool that is close to sufficient; the missing piece is error/not-found behavior and whether name lookups are exact.

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%, so both parameters are already documented, including the region enum values and 'Omit for all'. The description repeats the id-or-name flexibility without adding format hints (e.g. whether names are fuzzy-matched) or clarifying what 'all regions' means for the output, so the baseline of 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?

The description names the resource ('One product') and enumerates exactly what comes back: rank and share per category, 12-month share history, and regional prices with shop links. That is far more specific than the title alone, though it never names a sibling (e.g. compare_products, search_products) it should be preferred over.

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?

The framing 'One product' implies a single-entity lookup rather than a comparison or search, but the description never states when to use this instead of compare_products or search_products, nor any prerequisites. The only caller guidance is the input note 'Accepts an id or a name', which is parameter-level, not usage-level.

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