Skip to main content
Glama
Sign In
Sous

Sous

by Zawaer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Optional: Product details

get_product
Read-onlyIdempotent

Retrieves full static product details by product ID, including names, pack sizes, allergens, claims, labels, reliability, and CO2 estimate; price and stock are excluded.

Instructions

Full static details of one product: names, pack sizes, allergens, claims, labels, reliability, CO2 estimate.

No price or stock: those come only from request_quote.

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
idYes
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the useful 'static' framing that the returned data is not live pricing/inventory, but says nothing about missing-product behavior or freshness of the static attributes.

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?

Two tight sentences, payload scope front-loaded and the price/stock exclusion second. The field enumeration is somewhat redundant with the output schema, but it is compact and readable.

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?

An output schema exists, so return-value explanation is optional and the field list is a bonus. For a one-parameter read tool with rich annotations, the only real omission is how to obtain a valid product_id and what happens when it's invalid.

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 description coverage is 0% for the single product_id parameter, so the description must carry the burden. 'One product' implies a single-product identifier but gives no format, source-of-ID, or error semantics, so it only partially compensates for the coverage gap.

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?

States a specific verb+resource ('Full static details of one product') and enumerates the exact payload (names, pack sizes, allergens, claims, labels, reliability, CO2 estimate). The second sentence separates it from price/stock retrieval, so an agent can distinguish it from request_quote without inspecting schemas.

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?

Explicitly routes price and stock questions to request_quote ('those come only from request_quote'), which is a concrete when-not-to-use rule. It does not say how to obtain a product_id or how this differs from search_products for discovery, leaving some selection inference to the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools