Skip to main content
Glama

getecoback-climate-weather

energiebuch_monatslaeufe_abdeckung

Read-only

Jahresübersicht mit belegten, geschätzten und fehlenden Monaten vor einem Vergleich kennzeichnen — Separate evidence coverage from a complete annual total.

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": {
      "berichtet_monate": "<berichtet_monate>",
      "geschaetzt_monate": "<geschaetzt_monate>",
      "bestaetigt_cent": "<bestaetigt_cent>",
      "geschaetzt_cent": "<geschaetzt_cent>"
    },
    "name": "energiebuch_monatslaeufe_abdeckung"
  }
}

Input Schema

NameRequiredDescriptionDefault
bestaetigt_centYesKosten der bestätigten Monate in Cent.
geschaetzt_centYesKosten der geschätzten Monate in Cent.
berichtet_monateYesMonate mit bestätigten Einzelwerten.
geschaetzt_monateYesZusätzliche geschätzte Monate, ohne Dopplung mit bestätigten Monaten.

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 establish this as a safe read-only, non-open-world operation. The description adds the useful conceptual behavior that evidence coverage should be separated from a complete annual total, but it does not explain how missing months are derived or what the marking output looks like.

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 definition is compact and front-loads the annual overview purpose. The bilingual gloss partially repeats the German sentence, but it remains short and structurally clear.

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 analysis tool, the schema documents inputs fully, but the description does not clarify the output classification, how missing months are determined, or edge cases such as overlapping month counts. It is adequate but leaves important behavioral context implicit.

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 the schema already defines all four numeric parameters. The description mentions evidenced, estimated, and missing months, which loosely relates to the parameters, but adds no syntax, constraints, or validation semantics beyond the schema.

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 action: marking an annual overview by evidenced, estimated, and missing months before a comparison. It is clearer than a tautology and distinguishes the tool from a pure comparison tool, though the German phrasing is somewhat abstract and no sibling is named.

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 phrase 'vor einem Vergleich' implies this is a preparatory coverage-check step before comparison. However, it gives no explicit when-not-to-use guidance and does not name alternatives, so usage is only implied.

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