Skip to main content
Glama

getecoback-climate-weather

stromgeraet_anschaffung_monatsbuch

Read-only

Einen gezahlten Gerätebetrag in der eigenen Monatsübersicht centgenau verteilen und laufenden Strom getrennt zeigen — Track a historical purchase and metered electricity without booking the purchase twice.

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": {
      "anschaffung_cent": "<anschaffung_cent>",
      "verteil_monate": "<verteil_monate>",
      "laufend_monat": "<laufend_monat>",
      "betrieb_cent": "<betrieb_cent>"
    },
    "name": "stromgeraet_anschaffung_monatsbuch"
  }
}

Input Schema

NameRequiredDescriptionDefault
betrieb_centYesGemessene variable Stromkosten dieses Monats in Cent.
laufend_monatYesNummer des Monats ab Kaufmonat, der zuerst als 1 gezählt wird.
verteil_monateYesSelbst gewählte ganze Anzahl an Monaten für die Vergleichsansicht.
anschaffung_centYesTatsächlich gezahlter Kaufpreis abzüglich belegter Erstattungen in Cent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 clear. The description adds useful behavioral context by saying the purchase should not be booked twice and that ongoing electricity is shown separately. However, it does not explain the calculation behavior or what the tool returns.

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 description is compact and front-loads the core operation before the English clarification. The bilingual repetition is somewhat redundant but still easy to parse and does not obscure the main purpose.

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 calculation-style tool with no output schema, the definition does not explain how the monthly allocation is computed or what result the agent should expect. Annotations cover the read-only, closed-world behavior, but the description omits important context about the tool's output.

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 are already documented in detail. The description reinforces the cent-level and separate-electricity framing but does not add parameter-specific meaning beyond what the schema provides.

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 operation: distributing a paid device amount cent-exactly across a monthly overview while showing ongoing electricity separately. It clearly frames the tool as tracking a historical purchase plus metered electricity without double-booking the purchase. No sibling differentiation is provided, but the purpose is understandable.

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 when-to-use or when-not-to-use guidance, and no alternative tool is named. The phrase 'Track a historical purchase and metered electricity' implies context, but an agent is left to infer when this tool is appropriate versus other calculation or ledger tools.

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