Skip to main content
Glama

The Builders Supply catalog

Get product details

get_product
Read-onlyIdempotent

Everything the store publishes about one product by SKU: description, attributes, finish and grade, dimensions and weight with units, order multiples, availability state with its meaning, lead time, images, documents, categories and the product page link.

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": {
      "sku": "<sku>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuYesstore SKU, e.g. SCH_02007

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds some domain context such as availability state with its meaning and lead time, but it focuses mostly on return fields and omits behavior for missing SKUs or exact lookup semantics.

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 a single front-loaded sentence with no filler, but its long enumeration of return fields is partly redundant with the existing output schema and would be tighter as a scope statement rather than a field list.

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 simple single-product read tool with annotations covering safety and an output schema covering return values, the description is complete enough to call it correctly. The main minor gap is that it does not say what happens when the SKU is not found.

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?

There is only one parameter and schema description coverage is 100%, so the schema already documents the SKU fully. The description adds no format, normalization, or lookup meaning beyond saying 'by SKU', which matches the baseline for fully covered parameters.

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 states a specific verb and resource — retrieving everything the store publishes about one product by SKU — and the singular 'one product' distinguishes it from sibling tools like search_products and browse_category.

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 by 'by SKU' and 'one product'; the description does not explicitly say when to use this versus search_products, compare_products, or check_availability, nor does it state when not to use it.

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