Skip to main content
Glama

taufnaus Geschenke-Shop

Produkte suchen

search_products
Read-onlyIdempotent

Search products across all taufnaus shops (or one shop). Understands meaning: describe the wish in natural language, e.g. 'Taufgeschenk für ein Mädchen, etwas Bleibendes, bis 40 Euro'. Returns product_id, shop, name, price (EUR incl. VAT), availability, image and url.

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": {
      "query": "<query>"
    },
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoOptional: age of the recipient in years
shopNoOptional shop slug from list_shops
limitNoMax results (default 8, max 20)
queryYesWhat the customer is looking for, in natural language
max_priceNo
min_priceNo
recipientNoOptional: for whom (e.g. kind, baby, frau, mann, paar)
only_in_stockNoDefault true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 behavior, so the safety profile is covered. The description adds value beyond that by enumerating the returned fields (product_id, shop, name, price incl. VAT, availability, image, url), which matters because there is no output schema. It does not mention result ranking, empty-result behavior, or how min/max price interact with the semantic query.

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?

Three sentences with no filler: purpose and scope first, query-formulation guidance with a concrete example second, return contract last. The example is long but is the highest-value sentence for a semantic search tool, so it earns its place.

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?

For an 8-parameter read-only search with no output schema, the description covers purpose, query style, scope, currency and return fields, which is most of what an agent needs. It omits ranking/relevance behavior, default result ordering, and what an empty result set looks like, which keeps it short of complete.

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 75%, so most parameters are already documented; the description still adds meaning by clarifying that query is free-form natural language and by pinning the price filters to EUR including VAT. It does not explain min_price/max_price edge behavior or how recipient/age interact with the free-text query, which is the remaining gap in 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?

The description gives a specific verb and resource ("Search products") plus the scope ("across all taufnaus shops (or one shop)") and identifies the search as semantic/natural-language rather than keyword based. It does not explicitly name the sibling it differs from (e.g. get_product for a single known item, find_related_products for recommendations), so the differentiation is implied rather than stated.

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?

The description does tell the agent how to formulate input ("describe the wish in natural language") and supplies a concrete example, which is genuine usage guidance for the query parameter. It gives no when-to-use/when-not-to-use guidance against alternatives such as get_product or find_related_products, leaving routing to the agent's inference from the tool names.

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