Skip to main content
Glama

AIFEC

get_product

Read-only

Everything the shop says about one product: description in plain text, key facts, the options (colour, size) with their available values, variants with price and availability, delivery time and frequently asked questions. Call it whenever the customer asks about a product ("tell me about it", "what is it", "features") and answer with what it says.

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

Input Schema

NameRequiredDescriptionDefault
idYes
session_idNoOnly if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With readOnlyHint=true already supplied, the description's marginal value is that it specifies the breadth of returned data, including live-ish signals like price, availability and delivery time, which helps the agent know it need not chain other calls. It does not cover failure behavior (invalid or unknown id) or whether variant availability is real-time, so it is good but not complete.

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 sentences, front-loaded with the payload contents and followed by the call trigger and response guidance. No filler, though the long comma-delimited content list in sentence one is dense and could be grouped more crisply.

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 no output schema, the description usefully substitutes by enumerating return contents, and the session_id parameter is covered by the schema. The main remaining gap is provenance of the required id (presumably from search_products or list_categories), which an agent must infer.

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?

The description adds nothing about parameters. Schema coverage is 50%: session_id is fully documented in the schema, while id is bare except for type and minimum. With half the parameters self-documented and the other half trivially named, baseline 3 is appropriate.

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 resource (one product) and enumerates exactly what comes back: plain-text description, key facts, options (colour, size) with values, variants with price and availability, delivery time, and FAQs. The 'one product' scope makes it distinguishable from list-oriented siblings like search_products without needing to name them.

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 an explicit trigger condition ("whenever the customer asks about a product") backed by concrete phrasings such as "tell me about it", "what is it", "features". It stops short of any exclusion or alternative — e.g. it never says to use search_products first to obtain an id, nor when not to call 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