nanion.com (Vaia)

frage

Read-onlyIdempotent

Answers a question about nanion.com from the company's own website, with numbered sources, in the language of the question. If the question names two products and a comparison, a side-by-side of the technical data is added. What the website does not say is not answered. For a follow-up in the same conversation pass the id of the previous answer as “nach”.

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

Input Schema

Name	Required	Description	Default
`nach`	No	Id of the previous answer (for follow-up questions)
`frage`	Yes	The question in natural language

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and closed-world, so the remaining burden is light and the description still adds real behavior: answers are grounded only in website content and refuse otherwise, sources are numbered, the answer mirrors the question's language, and comparison questions yield a technical side-by-side. It does not say what happens with an invalid or stale 'nach' id.

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?

Three sentences, front-loaded with purpose and answer shape, then the comparison special case, then follow-up mechanics. No filler, though the middle sentence packs multiple behaviors together.

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?

No output schema exists, so the description carries the return-shape duty and does so by specifying numbered sources, question-language output, and a comparison table. Grounding and refusal rules are stated; only edge-case behavior for out-of-scope questions or bad follow-up ids is unaddressed.

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% and both parameters are documented, so the schema does the heavy lifting. The description adds meaning only for 'nach' (previous answer id, used for follow-ups) and frames 'frage' as natural language, without format constraints or examples.

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?

Names a specific verb and resource: answers questions about nanion.com using the company's own website, with numbered sources in the question's language. This is clearly distinct from siblings like produkt, produkte and vergleich, which expose product data directly.

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 conditions: use it for questions, pass the previous answer's id as 'nach' for follow-ups in the same conversation, and it will add a side-by-side for two-product comparisons. It also states a firm boundary ('what the website does not say is not answered'), but never explicitly routes comparison or product-lookup needs to the sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All nanion.com (Vaia) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?