Skip to main content
Glama

getecoback-raumklima

stromrechnung_steuerbasis_abgleich

Read-only

Netto-, Steuer- und Bruttobetrag einer Stromrechnungsposition rechnerisch abgleichen. — Reconcile net, gross and the stated tax rate for one bill line.

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": {
      "netto": "<netto>",
      "brutto": "<brutto>",
      "steuer_prozent": "<steuer_prozent>"
    },
    "name": "stromrechnung_steuerbasis_abgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
nettoYesNettobetrag in Euro für eine einzelne Position.
bruttoYesBruttobetrag in Euro derselben Position.
steuer_prozentYesAuf dieser Position ausgewiesener Prozentsatz.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a closed-world, non-mutating computation, and 'rechnerisch abgleichen' is fully consistent with that. What remains undisclosed is the outcome behavior: whether a mismatch yields a boolean, a delta, or an error, and whether tolerance/rounding is applied. With no output schema, that is a real gap, but it is a moderate one given the annotation coverage.

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, front-loaded sentences with no filler. The German/English duplication is the only inefficiency — each sentence restates the other — but the mirrored phrasing is clearly deliberate for a bilingual toolset and does not obscure the core action.

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 three inputs are documented in both schema and description, and the tool is a simple read-only computation, so the core is covered. However, with no output schema, the description should say what a successful versus failed reconciliation looks like; that return-value behavior is entirely absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above that by stressing 'derselben Position' / 'one bill line', which encodes the key constraint that all three values must come from the same line item, and by calling the rate 'ausgewiesen' (as stated on the bill). Those two points add meaning the schema alone does not convey.

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 gives a specific verb plus resource: 'Netto-, Steuer- und Bruttobetrag einer Stromrechnungsposition rechnerisch abgleichen' — a computational reconciliation of three named amounts for one bill line. An agent can immediately tell this is an arithmetic consistency check rather than a lookup or a mutation. It does not explicitly differentiate itself from any sibling, so it stops short of a 5.

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?

Scope is implied by 'einer Stromrechnungsposition' / 'one bill line', which tells the agent this operates on a single position rather than a whole invoice. There is no statement of when to reach for this versus other reconciliation-style siblings, no prerequisites, and no note on what to do when the values fail to reconcile.

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