Skip to main content
Glama

getecoback-raumklima

stromlogger_kurzereignis_stichprobe

Read-only

Prüfen, ob ein kurzes Ereignis zwischen gleichmäßigen Punktmessungen verpasst werden kann — Check whether a short load episode can fall between point samples.

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": {
      "raster_s": "<raster_s>",
      "ereignis_s": "<ereignis_s>"
    },
    "name": "stromlogger_kurzereignis_stichprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
raster_sYesKonstante Zeit zwischen zwei aufgezeichneten Momentanwerten, in Sekunden.
ereignis_sYesGemessene oder untersuchte Dauer des Leistungsereignisses, in Sekunden.

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 the safety profile is covered and the description need not restate it. The description adds that this is a coverage/sampling-gap judgment rather than a data retrieval, but it never says what the answer looks like (boolean verdict, ratio, threshold) despite there being no output schema. That is a meaningful gap for a computation tool.

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?

A single front-loaded sentence that leads with the verb and the core question, with no filler. The German/English duplication is defensible for a bilingual tool set, though it roughly doubles length for no informational gain.

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 two-parameter, closed-world read-only computation the scope is adequately bounded, but with no output schema the description should state the form of the result and the decision criterion (e.g. event shorter than the sampling interval is missed). As written, an agent knows what to pass in but not what to expect 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% and both parameters carry precise German descriptions (constant time between recorded instantaneous values; measured or investigated duration of the load event). The description reinforces the meaning by tying 'gleichmäßige Punktmessungen' to the raster and 'kurzes Ereignis' to the event duration, so semantics are unambiguous even if nothing new is added 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 specific operation ('Prüfen, ob ... verpasst werden kann' / check whether a short load episode can fall between point samples) with both the resource (point-sampled measurement series) and the question being answered. It is clearly distinguishable from sibling sampling tools such as saugroboter_ergebnis_stichprobe by focusing on the sampling-interval versus event-duration coverage question, though it does not explicitly name an alternative.

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 only implied: the pairing of 'gleichmäßigen Punktmessungen' with raster_s and 'kurzes Ereignis' with ereignis_s suggests the tool applies when checking sampling adequacy, but there is no explicit statement of when to use it, when not to, or which sibling to prefer. An agent must infer the scenario from the parameter names.

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