Skip to main content
Glama

taufnaus Geschenke-Shop

Produktdetails

get_product
Read-onlyIdempotent

Details of one product: description, images, attributes, pack sizes (variant_id, price, available quantity) and the maximum orderable quantity.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 is covered. The description adds genuine value by disclosing the shape of the payload, including variant-level pack sizes with variant_id, price and available quantity, plus the maximum orderable quantity — information an agent cannot get from the annotations. Missing only edge behavior such as what happens for an unknown product_id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with no filler. The parenthetical is an efficient way to expand 'pack sizes' without a second sentence, and every clause carries information about the response.

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 and no annotation-level return info, the description correctly takes on the job of describing the response fields, which it does at a useful level of granularity. A read-only single-parameter getter does not need much more; only the product_id format and not-found behavior are absent.

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% and the single parameter carries no inline documentation, so the description is the only source of meaning. It conveys that product_id identifies exactly one product, but never states the identifier format (numeric id vs SKU vs slug), which is the one thing an agent most needs beyond the schema.

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: 'Details of one product', immediately distinguishing a single-item detail fetch from catalog-style siblings such as search_products or list_shops. The enumeration of returned fields (description, images, attributes, pack sizes) further pins down what 'details' means, though the verb is nominal ('Details of') rather than an explicit action.

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: 'one product' plus a required product_id signals a lookup of an already-known product rather than discovery. There is no explicit statement that a product_id must first be obtained elsewhere, and no mention of when to prefer this over find_related_products or search_products.

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