Skip to main content
Glama

Get product details and specs

get_product
Read-only

USE THIS before you recommend one specific item, or when the human asks for the specs (shank size, piece count, material, coating). Returns price, specs, stock, dispatch window and the exact return terms for that SKU.

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_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the return contents — price, specs, stock, dispatch window, and exact return terms — which matters since there is no output schema. It leaves out edge behavior such as what happens for an unknown or discontinued SKU.

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?

One tight sentence with the usage trigger front-loaded in capital letters and the payoff (returned fields) immediately after. Every clause earns its place; nothing is redundant with the schema or annotations.

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 single-parameter read tool with no output schema, the description covers what it returns and when to reach for it, which is most of what an agent needs. The remaining gap — identifier format and failure behavior for invalid SKUs — is modest but real.

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 0% and the single product_id parameter has no description in the schema. The description partially compensates by framing the lookup around 'one specific item' and 'that SKU', implying product_id is a SKU-level identifier, but it never says the expected format or where to obtain a valid ID.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a specific verb and resource ('Get product details and specs') with an enumerated payload — price, specs, stock, dispatch window, return terms for a SKU. That level of detail separates it from siblings like check_stock (a single-signal lookup) and search_products (discovery) without either schema being opened.

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?

It gives a concrete trigger: call this before recommending a specific item, or when the human asks for specs. That is clear usage context. It stops short of exclusions or naming alternatives — it never says 'use search_products to find candidates first' or 'use check_stock if you only need availability' — so routing is implied rather than spelled out.

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