Skip to main content
Glama

getecoback-raumklima

haushaltsenergie_auslage_ausgleichen

Read-only

Gemeinsame Energierechnung zwischen zwei Personen nach bereits geleisteten Auslagen und Rückzahlungen ausgleichen — Settle a shared utility bill after prior reimbursements.

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": {
      "vorgestreckt_a_cent": "<vorgestreckt_a_cent>",
      "vorgestreckt_b_cent": "<vorgestreckt_b_cent>",
      "vereinbarter_anteil_a_cent": "<vereinbarter_anteil_a_cent>",
      "netto_b_an_a_cent": "<netto_b_an_a_cent>"
    },
    "name": "haushaltsenergie_auslage_ausgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
netto_b_an_a_centYesFrühere Erstattungen von B an A abzüglich solcher in Gegenrichtung in Cent.
vorgestreckt_a_centYesDirekt an den Anbieter gezahlte Auslage von A in Cent.
vorgestreckt_b_centYesDirekt an den Anbieter gezahlte Auslage von B in Cent.
vereinbarter_anteil_a_centYesFrei vereinbarter finaler Kostenanteil von 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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description doesn't need to repeat it. What it does add — that prior reimbursements are netted in — is useful context beyond the annotations. It does not state that the tool only computes a figure and persists nothing, nor how the result is expressed (who owes whom, sign of the returned amount), which is the main behavioral fact an agent needs here.

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?

A single sentence, front-loaded with the shared-bill context and then the netting condition, with no filler. The bilingual German/English duplication is slightly redundant but aids disambiguation of a long compound tool name and doesn't obscure the content.

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?

All four required parameters are fully described and there are no nested objects, so the input side is complete. But with no output schema, the description is the only place the return value could be characterized, and it says nothing about what the settlement figure represents or its sign convention — a meaningful gap for a calculation tool whose entire purpose is producing one number.

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 each of the four cent-valued parameters is already documented in the schema, making 3 the baseline. The description's phrase about prior reimbursements corroborates the meaning of netto_b_an_a_cent but adds no format, sign, or boundary detail (e.g. how the negative minimum is used) beyond what the schema states.

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 verb+object in both German and English: settling a shared utility bill between two people, explicitly accounting for prior expenditures and repayments. An agent can tell this is a netting/settlement computation rather than a simple split. It stops short of 5 because it doesn't position itself against any alternative (e.g. a plain cost-split calculation), and the sibling list offers no obvious candidate to differentiate 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?

The clause 'nach bereits geleisteten Auslagen und Rückzahlungen' implies the scenario in which this tool is the right one (when prior money has already moved between the parties), which is genuine implied guidance. However there is no explicit when-to-use/when-not statement, no preconditions, and no named alternative for the simpler case of splitting a bill with no history.

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