Skip to main content
Glama

getecoback-raumklima

gemeinsame_energiekosten_cent_rest

Read-only

Einen vereinbarten Rechnungsbetrag mit drei ganzzahligen Gewichten centgenau verteilen — Allocate all cents using a largest-remainder split with a declared tie-break.

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>",
      "gewicht_a": "<gewicht_a>",
      "gewicht_b": "<gewicht_b>",
      "gewicht_c": "<gewicht_c>"
    },
    "name": "gemeinsame_energiekosten_cent_rest"
  }
}

Input Schema

NameRequiredDescriptionDefault
gewicht_aYesGanzzahliges vereinbartes Gewicht von A.
gewicht_bYesGanzzahliges vereinbartes Gewicht von B.
gewicht_cYesGanzzahliges vereinbartes Gewicht von C.
kosten_centYesZu verteilende nichtnegative Kosten in ganzen Cent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false, so the real value-add is the description's disclosure of the allocation algorithm: largest-remainder rounding, cent-exact output, and a deterministic tie-break. The remaining gap is that the tie-break rule itself is not named and zero-weight behavior is not addressed.

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 short and front-loaded, leading with the allocation action before the algorithm. The bilingual German-then-English restatement is mildly redundant but costs little.

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 stateless read-only computation with full schema coverage this is nearly sufficient, but with no output schema the description never indicates what is returned (presumably three cent amounts summing to the total) or the output field names. Edge-case behavior (all weights zero, rounding when the total does not divide evenly) is also unstated.

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 four parameters (kosten_cent and the three Gewichte) are already documented with ranges and meanings. The description only restates 'drei ganzzahlige Gewichte' and the cent unit, adding no new semantics such as what a zero weight means.

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 verb and resource ('Einen vereinbarten Rechnungsbetrag ... centgenau verteilen') plus the exact algorithm (largest-remainder split), so an agent knows precisely what the tool computes. It does not, however, contrast itself with any sibling tool, leaving differentiation to the naming.

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 statement of when to use this tool versus alternatives, no prerequisites, and no exclusion of edge cases. The usage context (splitting a shared bill by three weights) is only inferable from the verb, not stated as guidance.

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