Skip to main content
Glama

an_vertrieb

Hands a request on behalf of the buyer to the vareen.net 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

NameRequiredDescriptionDefault
nachNoId of the last answer (conversation context for the team)
nameNoThe buyer's name
emailYesThe buyer's e-mail address
firmaNoCompany
abgleichNoId of a requirement check (its result goes to the team)
anliegenYesWhat the request is about
freigabeYestrue = the buyer has explicitly agreed to pass on these details (required)
nachrichtNoMessage
zeitrahmenNoe.g. “Q1 2027”, “purchase within 3 months”
anforderungenNoThe buyer's technical requirements
offene_fragenNoQuestions still to be clarified
naechster_schrittNoDesired next step

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / name / description
      Added value: +"The buyer's name"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare a non-read-only, open-world, non-idempotent call, and the description adds the crucial behavioral fact that the result arrives asynchronously by e-mail from a human team rather than as an immediate tool response. It does not state expected latency or whether duplicate submissions create duplicate tickets, so it stops short of a 5.

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 followed by the consent constraint; nothing is padded. The consent clause slightly overlaps with the required 'freigabe' field, which is a minor redundancy.

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 12-parameter handoff tool with no output schema, the description covers the essential unknowns: who receives the data, that a human replies, and that consent is mandatory. It omits what confirmation the agent gets after calling and how the 'nach'/'abgleich' context references are used, leaving a small gap.

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 all twelve fields are already documented in the schema; the description adds essentially no extra field-level meaning. Baseline 3 applies when the schema carries the semantic load.

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 ('Hands a request on behalf of the buyer to the vareen.net team') and scopes it to binding information on prices, quotes, contracts and commitments. It is clear what the tool does, but it never mentions the sibling tool 'frage' to distinguish the two.

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 phrase 'Only use with the buyer's consent' is a real precondition for use, which is more than nothing. However, there is no guidance on when to prefer 'frage' instead, and the consent rule is already enforced by the required 'freigabe' parameter.

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