Skip to main content
Glama

getecoback-raumklima

energiekosten_eigener_anteil_deckel

Read-only

Einen gemeinsam vereinbarten Höchstanteil pro Person anwenden und den Kapazitätsrest getrennt zeigen — Reallocate a capped shared bill using agreed capacities.

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": {
      "kosten_cent": "<kosten_cent>",
      "vorschlag_a_cent": "<vorschlag_a_cent>",
      "deckel_a_cent": "<deckel_a_cent>",
      "deckel_b_cent": "<deckel_b_cent>"
    },
    "name": "energiekosten_eigener_anteil_deckel"
  }
}

Input Schema

NameRequiredDescriptionDefault
kosten_centYesGemeinsame Kosten in Cent.
deckel_a_centYesVereinbarter maximaler Anteil A in Cent.
deckel_b_centYesVereinbarter maximaler Anteil B in Cent.
vorschlag_a_centYesVorläufiger Anteil A in Cent.

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?

The readOnlyHint and openWorldHint annotations already establish a safe, closed-world calculation, and the description adds that residual capacity is reported separately. It does not disclose the allocation formula, edge-case behavior, or result structure, so behavioral transparency is moderate.

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?

The core German sentence is compact and front-loaded, and the English gloss mirrors it without adding technical detail. The bilingual duplication is mild redundancy, so it is efficient but not maximally tight.

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 four-parameter read-only calculation with no output schema, the definition covers the purpose and one output trait—separate capacity remainder—but omits computed allocation details and the return shape. It is callable from the schema, but not fully specified.

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%, so the four parameters are already fully documented; the description contributes conceptual framing around shared cost, agreed caps, and the provisional A share, but no new parameter-level semantics or format details.

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 names a specific operation: applying an agreed per-person cap to a shared bill and showing the remaining capacity separately. It reads clearly as a capped allocation/reallocation calculation, though it does not explicitly differentiate itself from any sibling tool.

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?

It supplies a usage context—reallocating a shared bill under agreed caps—but gives no explicit when-to-use or when-not-to-use rule and names no alternative. An agent must infer that this is for capped shared-cost splits rather than general cost arithmetic.

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