Skip to main content
Glama
catalog-mcp

catalog-mcp

by Yehiak

Get product

get_product
Read-onlyIdempotent

Retrieve a complete product record by Amazon ASIN, including features, description, category path, and specification table for detailed catalog lookups.

Instructions

Get the full record for one product: features, description, category path and spec table.

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
product_idYesAmazon parent ASIN, e.g. 'B07XYZ1234'.
max_description_charsNoTruncate the description to this many characters (0 = omit).

Output Schema

NameRequiredDescriptionDefault
brandYesBrand from the product details, falling back to the store name.
priceYesPrice in USD when the listing had one (about half do).
storeYes
titleYes
detailsYesSpec table from the listing (dimensions, model number, ...).
categoryYesCatalog category, e.g. 'Appliances' or 'Video_Games'.
featuresYesBullet points from the listing.
image_urlYes
categoriesYesCategory path from broad to narrow.
product_idYesAmazon parent ASIN. Pass it to get_product, compare_products or find_near_duplicates.
descriptionYesListing description, truncated to max_description_chars.
main_categoryYes
rating_numberYesHow many ratings the average is based on.
average_ratingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered by structured data. The description adds little beyond that — it lists record sections but says nothing about error behavior, whether the parent ASIN expands to child variants, or truncation effects (left to the schema).

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 front-loaded sentence with the verb first and the returned sections enumerated after the colon. 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?

For a two-parameter, read-only lookup with full schema coverage, rich annotations and an output schema, the description is largely sufficient — return values need not be explained. Minor gap: no note on what happens when the ASIN is not found or when description truncation alters the payload.

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 product_id (ASIN pattern, example) and max_description_chars (truncation, 0 = omit) are fully documented in the schema. The description adds no parameter-level meaning beyond 'full record', 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?

States a specific verb ('Get') and resource ('the full record for one product') and enumerates the record's contents: features, description, category path and spec table. It implicitly distinguishes itself from search_products by fetching a single known product rather than searching, though it never names a sibling explicitly.

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: the required product_id makes it obvious this is the lookup-by-ID path, and 'full record' hints at using it after a search. There is no explicit when-to-use versus search_products or compare_products, and no stated preconditions or failure behavior for unknown ASINs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.