Skip to main content
Glama

getProduct

Product detail with structuredContent.card (USD). ALWAYS pass shipToCountry (ISO-2) when the human’s country is known — returns soft freight + price.approxLocal (e.g. ≈ A$23). Without it there is no local approx. Do not invent FX. Display: MCP App → host card → markdown. Then getReviews; quickCheckout to buy.

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": {
      "productId": "<productId>"
    },
    "name": "getProduct"
  }
}

Input Schema

NameRequiredDescriptionDefault
productIdYesProduct id or slug
shipToCountryNoISO-2 country when known (AU/US/GB/…). Required for soft shipping + approxLocal. Example: AU

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / shipToCountry / description
      Added value: +"ISO-2 country when known (AU/US/GB/…). Required for soft shipping + approxLocal. Example: AU"
  2. Changed1 schema field changed
    • addedInput schema / properties / shipToCountry
      Added value: +{
      +  "type": "string"
      +}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and delivers: it discloses the return payload (structuredContent.card in USD, price.approxLocal, soft freight), the degradation behavior when shipToCountry is absent, and a hard constraint ("Do not invent FX"). It omits auth, error, and rate-limit behavior, but the output-shape disclosure is the more valuable gap to close.

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?

Front-loaded with the resource and its return shape, then the parameter rule, then display and follow-up guidance — every clause carries information. The telegraphic style ("Display: MCP App → host card → markdown") is terse to the point of being slightly cryptic.

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?

There is no output schema, so the description must and does describe what comes back and how to render it, and it flags the one parameter that materially changes the result. For a two-parameter read tool this covers what an agent needs to call and present it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds real semantics the schema lacks: what shipToCountry actually changes (soft freight plus approxLocal), the example output format (≈ A$23), and the explicit prohibition on fabricating FX rates. productId gets no extra treatment, which the schema already handles.

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?

"Product detail" plus the named return shape (structuredContent.card in USD) gives a clear verb-and-resource read, and the trailing "Then getReviews; quickCheckout" positions it in a workflow. It does not explicitly distinguish itself from searchProducts, so the agent must infer the lookup-vs-browse split.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Strong conditional guidance on the optional parameter ("ALWAYS pass shipToCountry when the human's country is known") with a stated consequence for omitting it, plus explicit follow-up routing to getReviews and quickCheckout. No exclusion against sibling search tools, but the usage context is otherwise concrete.

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