Skip to main content
Glama

nanion.com (Vaia)

anforderungen_pruefen

Read-onlyIdempotent

Checks technical requirements against the data sheets of all (or selected) products: per product and requirement met / not met / unclear, with the supporting feature and source; products sorted by fit. “Unclear” means the information is missing or ambiguous — then follow up with “frage” or clarify via “an_vertrieb”.

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": {
      "anforderungen": "<anforderungen>"
    },
    "name": "anforderungen_pruefen"
  }
}

Input Schema

NameRequiredDescriptionDefault
produkteNooptional: check only these products
anforderungenYese.g. “at least 384 channels”, “temperature control”

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/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 genuinely new behavioral context: the per-product/per-requirement verdict structure, the meaning of 'unclear', the inclusion of supporting feature and source, and fit-based sorting. It does not discuss limits on how many products or requirements can be checked at once.

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 action and result shape, then the exception handling. Dense but every clause carries information; the quoted tool names are slightly noisy but functional.

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?

There is no output schema, so the description must carry the return-value burden, and it does: verdict categories, supporting evidence, source, and sort order are all specified. Combined with the follow-up routing for 'unclear', an agent has everything needed to call and interpret it.

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 coverage is 100%, so both parameters are already documented, including that 'produkte' is optional and the requirement string format. The description reinforces that omitting products means checking all of them, but adds no syntax or constraint detail beyond the schema. Baseline 3 applies.

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 and resource ('Checks technical requirements against the data sheets of all (or selected) products') and describes the result shape (per product and requirement: met/not met/unclear, with supporting feature and source, sorted by fit). This is enough for an agent to distinguish it from siblings like produkt or vergleich without opening a schema.

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?

Gives clear usage context and explicitly routes the ambiguous case: when a result is 'unclear', follow up with 'frage' or clarify via 'an_vertrieb'. It does not state when to prefer this over vergleich or produkt, so it stops short of full when/when-not guidance.

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