nanion.com (Vaia)

an_vertrieb

Hands a request on behalf of the buyer to the nanion.com team — for binding information on prices, quotes, contracts or individual commitments. Only use with the buyer's consent; the team replies by e-mail.

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": {
      "email": "<email>",
      "anliegen": "<anliegen>",
      "freigabe": "<freigabe>"
    },
    "name": "an_vertrieb"
  }
}

Input Schema

Name	Required	Description
`nach`	No	Id of the last answer (conversation context for the team)
`name`	No	The buyer's name
`email`	Yes	The buyer's e-mail address
`firma`	No	Company
`abgleich`	No	Id of a requirement check (its result goes to the team)
`anliegen`	Yes	What the request is about
`freigabe`	Yes	true = the buyer has explicitly agreed to pass on these details (required)
`nachricht`	No	Message
`zeitrahmen`	No	e.g. “Q1 2027”, “purchase within 3 months”
`anforderungen`	No	The buyer's technical requirements
`offene_fragen`	No	Questions still to be clarified
`naechster_schritt`	No	Desired next step

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Adds genuine context beyond the annotations: the request goes to an external human team, the reply arrives by e-mail, and buyer consent is mandatory. It does not disclose expected turnaround, what happens if the team cannot answer, or whether the buyer becomes committed by the handoff — meaningful gaps for a non-idempotent, open-world side-effecting call.

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?

Two sentences, zero waste, with the action front-loaded and the consent constraint and reply channel following. Every clause carries information an agent needs before calling.

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 a twelve-parameter tool with full schema coverage and no output schema, the description covers purpose, the consent gate, and the response channel (e-mail), which is enough to decide and invoke correctly. Failure behavior and turnaround time are the only notable omissions.

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 100%, so the twelve parameters are already fully documented, including the freigabe consent flag and the naechster_schritt enum. The description only references consent and the general topic, adding no format or selection guidance beyond the schema; baseline 3 applies.

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?

Names a specific action (handing a request on the buyer's behalf to the nanion.com team) and a precise scope (binding information on prices, quotes, contracts, individual commitments). That is clearly distinct from the informational siblings like produkt, produkte, vergleich and anforderungen_pruefen, though the description never names an alternative explicitly.

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 a real precondition — only use with the buyer's consent — and scopes usage to cases needing binding information rather than general product data. It stops short of naming when not to use it or which sibling to prefer for non-binding questions, so the routing is implied rather than stated.

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?