Skip to main content
Glama

getecoback-raumklima

stromexport_intervallstempel_tarifkante

Read-only

Ein Messintervall je nach Start- oder Endstempel relativ zur Tarifkante einordnen — Interpret a signed interval timestamp using its documented timestamp convention.

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": {
      "stempel_min": "<stempel_min>",
      "dauer_min": "<dauer_min>",
      "tarifwechsel_min": "<tarifwechsel_min>",
      "stempel_bedeutung": "<stempel_bedeutung>"
    },
    "name": "stromexport_intervallstempel_tarifkante"
  }
}

Input Schema

NameRequiredDescriptionDefault
dauer_minYesTatsächliche Dauer dieses Messintervalls.
stempel_minYesZeitstempel des Verbrauchsintervalls ab gemeinsamem Zeitnullpunkt.
tarifwechsel_minYesZeitpunkt des Preiswechsels auf derselben Uhr.
stempel_bedeutungYesIst der Zeitstempel als Beginn oder Ende des Intervalls dokumentiert?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 safety is covered. The description adds that the timestamp must be interpreted according to its documented convention and relative to a tariff edge, but it does not explain behavior for the 'unbekannt' convention, boundary cases, or what the result represents.

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 short and front-loads the core operation. The bilingual repetition is slightly redundant, but there is no wasted explanatory prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has four required parameters, an enum, and no output schema, so the description should clarify what 'einordnen' returns and how 'unbekannt' is handled. It does neither, leaving an agent with only a high-level interpretation statement.

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 documents all four parameters, including the enum for stempel_bedeutung. The description mentions start/end stamps, tariff edge, and timestamp convention, but it adds no syntax or interpretation details beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (Messintervall/Tarifkante) and verb (einordnen/interpret), so the general purpose is inferable. However, 'einordnen' is vague about what the classification actually produces, and the English sentence largely restates the German without clarifying the output.

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?

The description gives no explicit guidance on when to use this tool versus alternatives, nor does it name conditions or exclusions. It only implies that it is relevant for interpreting a timestamp with a documented convention.

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