Skip to main content
Glama

Get product details

get_product
Read-only

Fetch complete details for one product by id (e.g. roller-blockout, venetian-25mm-aluwood). Returns all available colours with in-stock status, materials, features, and maximum supported dimensions. Use before configure_product to confirm a colour exists and is in stock before committing. Duo Roller: colour is one blockout and one sheer written "Blockout + Sheer" (get_product returns duo_fabrics).

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

Output Schema

NameRequiredDescriptionDefault
nameYes
coloursYes
categoryYes
featuresNo
materialsNo
product_idYes
schema_urlNo
descriptionNo
product_urlYes
size_limitsNo
max_width_mmNo
suitable_forNo
max_height_mmNo
installation_typeNo
starting_price_zarNo
colour_count_in_stockNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioural context beyond that: the shape of the response (colours with in-stock status, materials, features, max dimensions) and the duo-specific rule that colour is a combined "Blockout + Sheer" string surfaced as duo_fabrics.

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 core action, then workflow, then the edge case. The final duo sentence is narrow but earns its place because it prevents a colour-selection error. No filler.

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 a single parameter and an output schema present, the description needn't document return values in detail, yet it summarizes them usefully. It covers id format, the pre-configuration role, and the duo fabric quirk. Only the relation to sibling inventory tools like check_colour_stock is left implicit.

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 0% and the single parameter is fully undocumented in the schema, so the description must compensate. It does so by supplying concrete id formats, which is the main ambiguity an agent would hit. It could go further on whether ids are slugs or catalog codes only implicitly, hence not a 5.

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?

"Fetch complete details for one product by id" gives a specific verb and resource, and the example ids (roller-blockout, venetian-25mm-aluwood) make the resource concrete. The enumeration of returned data and the contrast with configure_product let an agent tell this apart from the mutation sibling without opening either schema.

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 states an explicit precondition workflow: use this before configure_product to confirm a colour exists and is in stock. There is no explicit when-not guidance (e.g., the relationship to check_colour_stock or lookup_catalog is unstated), but the recommended sequencing is clear enough to act on.

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