Skip to main content
Glama

compatsy home espresso

Get product details

get_product
Read-onlyIdempotent

Full specs with per-field confidence and source, every offer with verified time, 30/90-day price range, and the top fits per category with counts. Example: {"product_id":"breville-barista-express"}

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_id": "<product_id>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
fits_limitNoFits listed per category (default 10; 0 = counts only). For one pair use check_fit
product_idYesProduct id or slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / fits_limit
      Added value: +{
      +  "description": "Fits listed per category (default 10; 0 = counts only). For one pair use check_fit",
      +  "maximum": 50,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is free to spend its words on payload behavior. It does so usefully — per-field confidence and provenance, verified offer timestamps, price-range windows — which is real context an agent cannot get from the annotations. It omits any note on response size, latency, or what happens with an unknown product_id.

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?

A single dense sentence followed by one concrete example — no filler and the most valuable information (what you get back) comes first. It reads as a payload inventory rather than a purpose statement, which makes the opening slightly harder to parse than a verb-led sentence would be.

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 largely discharges it by enumerating the response sections, which is exactly what an agent needs to decide whether to call it. Gaps remain around failure modes and how fits_limit shapes the response at the top level, but for a two-parameter read tool the coverage is solid.

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 fits_limit parameter already documents its default, maximum, and the check_fit alternative. The example value {"product_id":"breville-barista-express"} lightly illustrates the slug format the schema already mentions, so the description adds only marginal meaning beyond the structured fields.

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 payload precisely — full specs, offers with verified time, 30/90-day price range, and top fits per category with counts — which clearly marks this as the deep single-product detail tool rather than a search or comparison tool. It never states an explicit verb like 'retrieves' and never names a sibling, so sibling differentiation is only implicit through payload depth.

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?

Usage is only implied: an agent can infer it should call this when it needs comprehensive data for one known product. No when-not-to-use guidance, no prerequisites (e.g. that product_id must come from search_products), and the sibling routing (check_fit for one pair) appears only in the schema, not the description.

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.