Skip to main content
Glama

getecoback-raumklima

stromlogger_sequenz_counter_luecke

Read-only

Mit drei in Zeitreihenfolge exportierten Sequenznummern zwischen fortlaufenden, fehlenden und neu begonnenen Paketen unterscheiden — Audit packet counters separately from metered values.

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": {
      "erste_nummer": "<erste_nummer>",
      "zweite_nummer": "<zweite_nummer>",
      "dritte_nummer": "<dritte_nummer>",
      "ohne_neustart_dokumentiert": "<ohne_neustart_dokumentiert>"
    },
    "name": "stromlogger_sequenz_counter_luecke"
  }
}

Input Schema

NameRequiredDescriptionDefault
erste_nummerYesErste exportierte Paketnummer des durchgehend genutzten Senders.
dritte_nummerYesDritte exportierte Paketnummer desselben Senders.
zweite_nummerYesZweite exportierte Paketnummer desselben Senders.
ohne_neustart_dokumentiertYesIst ein Neustart oder Nummernumlauf in beiden Abständen ausgeschlossen und wird pro Paket um eins erhöht?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 analytic context. It does add that the result separates audit packet counters from metered values, but it never states the shape of the answer (single category? per-interval verdicts?) nor how the boolean qualifier changes the outcome.

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 operative condition is front-loaded in the first clause with no wasted preamble. The trailing half-sentence about auditing packet counters versus metered values is abstract and language-mixed, slightly weakening an otherwise tight two-part description.

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?

With four required params and no output schema, the description carries the burden of describing the return result; it partially does by naming three outcome classes, which is the essential contribution. It leaves unclear how the boolean restart-exclusion flag interacts with those classes and what an agent actually receives back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns a step above it by stressing that the three numbers must be in time order, which the schema field names alone do not convey. It adds nothing about the boolean 'ohne_neustart_dokumentiert' beyond what the schema already says, keeping it from 5.

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 operation: classify three sequence numbers taken in time order as consecutive, missing, or restarted packets. That is a specific verb-plus-resource statement an agent can act on. It does not name or exclude any sibling (e.g. the similar-looking 'stromlogger_kurzereignis_stichprobe' or 'verbrauchsmittel_zweite_packung_erst_bei_luecke'), so it falls short of 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 by the precondition 'drei in Zeitreihenfolge exportierten Sequenznummern' — you call it when you already have three exported counters in chronological order. There is no explicit when-not guidance and no alternative tool is named, so the agent must infer routing from the sibling list 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