Skip to main content
Glama

Babelii-Diofis Account

Rincian produk

get_product
Read-onlyIdempotent

Optional: full details of one product by a ref from search_products (search rows already carry what is needed to buy).

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_ref": "<product_ref>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_refYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 and closed-world, so the safety profile needs no restatement. The description adds the useful context that this call is supplemental rather than required. It says nothing about cost, latency, or whether the payload is larger/slower than a search row, which is the main behavioral trade-off here.

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?

One sentence, no filler, and the 'Optional' qualifier is front-loaded where it matters most. The parenthetical is dense but earns its space by carrying the differentiation from search_products. Slightly compressed phrasing costs a bit of readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need no explanation, and the single parameter's origin is documented. For a one-argument lookup whose annotations fully cover safety, nothing essential is missing.

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%, so the bare 'Product Ref' field gives no meaning on its own; the description supplies the crucial provenance, that the ref must come from search_products. That is exactly the semantics an agent needs to form a valid argument. It does not describe the ref's format or whether refs persist across sessions.

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

Purpose4/5

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

States a specific resource and scope: full details of one product, keyed by a ref. It also implicitly contrasts with search_products by noting search rows already contain purchase-relevant data, so the agent can distinguish the two. It stops short of naming what 'full details' includes.

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 frames itself as optional and says the ref comes from search_products, plus that search results already suffice to buy. That is real routing guidance for when to skip it. It does not state a positive condition for when the extra detail is actually needed.

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