Skip to main content
Glama

Muretai Catalog

Get one product

catalog.get_product
Read-only

Return one stored product of one indexed shop, chosen by the shop's origin (https://shop.example, or any page URL on it) and the product's permalink, or its sku where the catalog shows one. The answer is the same JSON as that product's entry in GET /catalog/shop/products.json?origin=: name, price, currency, stock, link and when the catalog read it. Stored data only: nothing is fetched. An unknown shop or product is refused by 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": {
      "origin": "<origin>"
    },
    "name": "catalog.get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuNoThe product's sku, where the catalog's entry shows one.
originYesThe shop's origin or a page URL on it (http or https).
permalinkNoThe product page URL, exactly as the catalog lists it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond readOnlyHint and openWorldHint=false, the description discloses that the operation is purely against stored data with no fetching, that error behavior is a named refusal for an unknown shop or product, and what the response payload contains. It does not cover empty/partial results or how freshness of the 'catalog read' timestamp behaves, which keeps it below full marks.

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?

Three sentences, front-loaded with the operation and scope, then the return shape, then the stored-only guarantee. It is dense but every sentence carries information; the reference to the equivalent GET endpoint is the one clause an agent may not need.

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 compensates by enumerating the returned fields (name, price, currency, stock, link, read time) and stating the storage guarantee and error behavior. It is nearly complete for a single-record read; only the permalink-vs-sku precedence when both are supplied is left unstated.

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%, so all three parameters are already documented, and the description largely restates that: origin may be a page URL on the shop, permalink is the listed URL, and sku exists only where the catalog shows one. It clarifies that permalink and sku are alternatives for identifying the product but adds no format or matching rules beyond the schema.

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 a specific verb and resource ('Return one stored product of one indexed shop') and pins down the two lookup keys, so an agent can tell it fetches a single record rather than a list. It stops short of explicitly contrasting itself with catalog.search or catalog.lookup, so sibling differentiation is implied by 'one' 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?

Useful context is present: stored data only, nothing fetched, and unknown shop or product is refused by name. However, there is no explicit statement of when to call this versus catalog.search or catalog.lookup, nor what to do when a product's sku is not shown in the catalog; the guidance is implied rather than directed.

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