Skip to main content
Glama

getecoback-raumklima

reparaturangebot_kostenband_deckel_nachtrag

Read-only

Angebotssumme, belegte Nachtragsgrenze und nicht begrenzte Zusatzposition als unterschiedliche Kostenevidenz erfassen — Bound documented repair expenditure only when every included extra is capped.

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": {
      "basis_euro": "<basis_euro>",
      "nachtrag_unten_euro": "<nachtrag_unten_euro>",
      "nachtrag_deckel_euro": "<nachtrag_deckel_euro>",
      "weitere_offene_kosten": "<weitere_offene_kosten>",
      "eigener_deckel_euro": "<eigener_deckel_euro>"
    },
    "name": "reparaturangebot_kostenband_deckel_nachtrag"
  }
}

Input Schema

NameRequiredDescriptionDefault
basis_euroYesFixer bestätigter Grundbetrag desselben Angebots.
eigener_deckel_euroYesEigene Obergrenze für dieses Angebot, ohne Aussage zu Rechten.
nachtrag_unten_euroYesBelegter minimaler Zusatz für eine bekannte Position.
nachtrag_deckel_euroYesBelegter oberer Zusatzbetrag für dieselbe Position.
weitere_offene_kostenYesKann eine weitere notwendige Position ohne belegte Obergrenze hinzukommen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the important rule that documented expenditure is bounded only when every included extra is capped, but it does not disclose output format or failure behavior.

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?

It is a single dense sentence that front-loads the evidence types and then states the capping rule, with no wasted clauses. Mixed German/English and compound jargon slightly reduce readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-required-parameter domain evaluator with no output schema, the definition states the key capping rule but not what result is produced or how the parameters combine into a bounded/unbounded outcome. That leaves the definition incomplete for reliable invocation.

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?

All five parameters are fully described in the schema, so the baseline is 3. The prose loosely maps quote sum, addendum bounds, and uncapped extra to the cost-evidence categories, but adds little parameter-level meaning beyond the schema, especially for eigener_deckel_euro.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a domain-specific operation—recording a quote sum, documented addendum bounds, and an uncapped extra as distinct cost evidence—and states a capping rule. However, 'erfassen' is ambiguous alongside readOnlyHint, and it never clarifies whether this validates, computes, or merely classifies the evidence; no sibling is named for differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use, when-not-to-use, or alternative routing guidance. The capping rule describes internal logic rather than when an agent should select this tool over other repair-quote tools.

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