Skip to main content
Glama

Storewire Lite demo store

Get product details

get_product
Read-onlyIdempotent

One product as its page on the Trailhead Supply website shows it: name, brand, model, page URL, photos, price, stock line, key specs, the full spec table by group, warranty, a plain-text description, documents with download links, and its category trail. similar lists alternatives; goes_with lists what it needs or works with, each with its relation.

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
localeNoAnswer language: en (default en). Names, labels and URLs follow it.
productYesThe product: its public_id from an earlier answer, its page URL or slug on the store's website, or the manufacturer model number.

Output Schema

NameRequiredDescriptionDefault
urlNoThe product page on the store's website, in the answer language; cite it.
nameNo
brandNo
imageNo
modelNo
priceNo
specsYes
badgesNoFor example new, sale or featured.
imagesYesUp to 4 photos, the main one first.
similarYesAlternatives, up to 6.
categoryNo
warrantyYes
documentsYes
goes_withYesUp to 6.
key_specsNo
public_idNoPass it to get_product or compare_products.
truncatedNoPresent and true only when the answer outgrew the size budget and its last list items were left out; ask narrower to see them.
breadcrumbYes
answer_typeNoWhat this answer is, for rendering.
descriptionYesPlain text, shortened.
availabilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral context by explaining the rich return shape, the meaning of the similar and goes_with relation lists, and the locale-sensitive nature of names and URLs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is front-loaded and has no filler, but the long enumeration of return fields duplicates the output schema and makes the single sentence hard to scan. The second sentence about similar and goes_with is the only part that adds real semantic value.

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?

Because an output schema exists, the description does not need to detail every return field. It still provides enough context about the product's page-like contents, related-item lists, and locale handling for an agent to understand the result, though it could briefly note failure modes for invalid identifiers.

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 schema already documents both product identifiers and locale. The description restates the kinds of product identifier accepted but adds no syntax, format, or edge-case meaning beyond what the schema provides.

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 uses a specific verb and resource ('Get one product') and enumerates the fields returned, making the tool's scope clear. The phrase 'One product' implicitly distinguishes it from list/search siblings, though no sibling is named directly.

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?

It implies this is the tool for retrieving details of a single product and notes that the product can come from an earlier answer or the store website. However, it never explicitly says when to use this instead of search_products, compare_products, or show_products.

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.