Skip to main content
Glama

getecoback-climate-weather

diagramm_hervorgehobener_schnitt_zeitreihe

Read-only

Einen hervorgehobenen Verbrauchsausschnitt relativ zur Länge des Gesamtprotokolls einordnen — Show how much of the record is represented by a selected chart window.

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": {
      "gesamte_messung_h": "<gesamte_messung_h>",
      "ausschnitt_h": "<ausschnitt_h>",
      "gesamtsumme_kwh": "<gesamtsumme_kwh>",
      "ausschnitt_kwh": "<ausschnitt_kwh>"
    },
    "name": "diagramm_hervorgehobener_schnitt_zeitreihe"
  }
}

Input Schema

NameRequiredDescriptionDefault
ausschnitt_hYesDauer der separat hervorgehobenen Messungen in Stunden.
ausschnitt_kwhYesTeilmenge des Stroms für denselben hervorgehobenen Messabschnitt.
gesamtsumme_kwhYesDazugehörige Stromsumme für das Gesamtprotokoll in kWh.
gesamte_messung_hYesVollständige Dauer des verfügbaren Protokolls in Stunden.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/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. Beyond that the description adds almost nothing behavioral: it never states what is returned (percentage, ratio, hours, or rounded value), and it doesn't address edge cases such as a segment longer than the total record. For a pure calculation tool with no output schema, the return shape is the one thing the description most needed to disclose.

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 sentences, front-loaded with the operation, with no filler. The German/English duplication is redundant in substance but functional for bilingual routing and costs little space.

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?

Four required numeric parameters are fully described by the schema and the read-only nature is covered by annotations, so the definition is callable as written. However, with no output schema the description should have said what the result looks like and how degenerate inputs are handled; that gap is the main thing missing for a computation tool.

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% and all four parameters are documented with units and bounds, so the baseline of 3 applies. The description reinforces the pairing (segment duration vs. total duration, segment kWh vs. total kWh) but adds no format or constraint detail 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 names a concrete computation: putting a highlighted consumption segment (ausschnitt) in relation to the length of the whole record. The English gloss 'Show how much of the record is represented by a selected chart window' makes the intent unambiguous. It loses a point only because the verb 'einordnen' is soft and it doesn't distinguish itself from any alternative (though the sibling list contains no obvious overlap).

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, no when-not-to-use, no prerequisite (e.g., that ausschnitt values must be a subset of the totals), and no named alternative. The only guidance is implicit in the stated purpose.

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