Skip to main content
Glama

getecoback-climate-weather

strommessung_zeitabdeckung

Read-only

Prüfen, wie viel einer Messperiode tatsächlich mit Messintervallen belegt ist. — Audit interval coverage before treating an electricity log as complete.

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": {
      "ziel_minuten": "<ziel_minuten>",
      "volle_intervalle": "<volle_intervalle>",
      "intervall_minuten": "<intervall_minuten>"
    },
    "name": "strommessung_zeitabdeckung"
  }
}

Input Schema

NameRequiredDescriptionDefault
ziel_minutenYesGesamte Untersuchungsdauer in Minuten.
volle_intervalleYesZahl eindeutiger, vollständiger beobachteter Intervalle.
intervall_minutenYesDauer eines vollständigen Intervalls in Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that this is a pre-validation audit step, but says nothing about what the result expresses (a ratio, a boolean completeness verdict, or the missing remainder), which matters for a tool with no output schema.

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?

It is short and the purpose is front-loaded. The German and English sentences are near-duplicates rather than complementary, so the second sentence consumes space without adding information.

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 pure calculation tool with fully specified parameters this is nearly sufficient, but with no output schema the description should indicate what the coverage result looks like and how partial or zero-interval cases are treated. That omission leaves an agent guessing about the return value.

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 three parameters (ziel_minuten, volle_intervalle, intervall_minuten) are already documented with units and bounds. The description's phrasing ('Messperiode', 'Messintervalle') loosely maps to them but adds no interpretation or edge-case guidance beyond the schema, making the baseline 3 correct.

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 concrete operation: determining how much of a measurement period is actually covered by measurement intervals, and frames it as an audit of an electricity log. That is a specific verb+resource, but it never distinguishes this tool from nearby siblings such as strommessung_messluecke_spannweite, which plausibly addresses adjacent gap questions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Audit interval coverage before treating an electricity log as complete' gives a clear triggering condition for calling the tool. It stops short of exclusions or naming an alternative for related gap/span questions, so the agent must infer the boundary itself.

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