Skip to main content
Glama

getecoback-climate-weather

geraeteverlauf_zyklus_randschnitt

Read-only

Angefangene und vollständig gemessene Gerätezyklen für den Verbrauch je Nutzung trennen — Keep cycles cut by the start or end of a log out of the complete-cycle mean.

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": {
      "vollstaendige_zyklen": "<vollstaendige_zyklen>",
      "kwh_vollstaendig": "<kwh_vollstaendig>",
      "kwh_anfangsfragment": "<kwh_anfangsfragment>",
      "kwh_endfragment": "<kwh_endfragment>"
    },
    "name": "geraeteverlauf_zyklus_randschnitt"
  }
}

Input Schema

NameRequiredDescriptionDefault
kwh_endfragmentYeskWh des angeschnittenen Zyklus am Ende, sonst 0. Beide Fragmente überschneiden sich nicht.
kwh_vollstaendigYeskWh ausschließlich der vollständig beobachteten Zyklen.
kwh_anfangsfragmentYeskWh des angeschnittenen Zyklus am Anfang, sonst 0.
vollstaendige_zyklenYesZahl vollständig beobachteter Zyklen mit gleichen Endbedingungen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 safety is covered and the description only needs to add computational behavior. It does add useful domain context (fragments are excluded so the mean reflects only complete cycles, and the two fragments do not overlap), but it never says what the call actually returns — the mean, a corrected total, or the separated components — which is the key behavioral fact for a read-only calculation.

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 compact sentences, front-loaded with the German statement of purpose and followed by an English clarification. The bilingual duplication is slightly wasteful but each version adds a nuance (the second spells out the 'keep out of the mean' rule), and there is no filler.

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?

With four required numeric inputs, no output schema, and no stated return value, the description leaves the agent unable to predict the result of the call. For a purely computational tool the output contract is the essential missing piece, and the description does not compensate for the absent output schema.

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 each parameter is documented in German, including the non-overlap guarantee for the two fragments, so baseline is 3. The description supplies conceptual framing for why the fragment and complete kilowatt-hour fields exist, but no additional syntax, unit conventions, or edge-case handling (e.g. zero complete cycles) 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 operation on a specific resource: separating partially observed device cycles (cut by log start/end) from fully observed ones so the fragments do not enter the complete-cycle mean. The bilingual restatement makes the intent unambiguous. It does not, however, differentiate itself from any sibling or state what value is ultimately produced, which keeps it short of a 5.

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?

Usage is implied rather than stated: the agent can infer the tool applies when a log begins or ends mid-cycle. There is no explicit when-to-use trigger, no exclusion, and no named alternative among the many sibling tools, so the agent must reason about applicability from the input names alone.

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