Skip to main content
Glama

getecoback-climate-weather

klima_zubehoerbudget_verteilreserve

Read-only

Ein Preislimit auf bereits bestätigte Klima-Zubehörteile und die noch ungeklärten Positionen aufteilen — Partition an accessory budget into verified quotes and remaining allowance.

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": {
      "budget_eur": "<budget_eur>",
      "feste_teile_eur": "<feste_teile_eur>",
      "reserviert_eur": "<reserviert_eur>",
      "offene_teile": "<offene_teile>"
    },
    "name": "klima_zubehoerbudget_verteilreserve"
  }
}

Input Schema

NameRequiredDescriptionDefault
budget_eurYesEigenes Gesamtbudget für notwendiges Zubehör in Euro.
offene_teileYesAnzahl weiterer noch nicht bepreister notwendiger Positionen.
reserviert_eurYesBetrag für bekannte Nebenkosten und Montagebedarf.
feste_teile_eurYesSumme der bereits passenden und bepreisten Teile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 and the description is consistent with a pure calculation. Beyond that it adds the notion of a price cap being divided, but it does not say whether the computation merely reports the residual allowance or enforces feasibility, nor what happens when the confirmed parts already exceed the budget.

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 short sentences, front-loaded with the operation and its scope, with no padding. The German and English sentences are verbatim duplicates, which is mildly redundant but does not obscure the core statement.

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

Completeness3/5

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

For a read-only, closed-world computation with four fully documented required parameters, most of what an agent needs is present. The notable gap is the absent output schema combined with no description of the result — an agent cannot tell whether it receives a per-item allowance, a residual figure, or a feasibility verdict, which matters when the whole point is allocating a budget.

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% with per-parameter descriptions and bounds, so the schema carries the load. The description adds relational meaning by framing budget_eur as a cap split between confirmed parts and open items, but it gives no indication of how offene_teile (a count) interacts with the euro amounts, which is the only genuinely ambiguous parameter.

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?

The description states a specific verb and object ('Ein Preislimit ... aufteilen' / 'Partition an accessory budget') and names the two buckets it partitions into: already confirmed accessory parts versus unresolved positions. It is clearly a budgeting allocation tool, distinguishable from the measurement/check siblings, though it does not name any sibling to route away from.

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?

Usage is only implied: the split between 'bereits bestätigte' and 'noch ungeklärte Positionen' signals this belongs to a budget reconciliation step. There is no explicit when-to-use, no prerequisites (e.g. that all amounts must be in EUR and mutually consistent), and no statement of when a different tool would be preferable.

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