Skip to main content
Glama

getecoback-climate-weather

raumlogger_ereignis_raster_grenzfall

Read-only

Einen unscharf protokollierten Lüftungsbeginn nur bei eindeutiger Lage einem Messintervall zuordnen — Assign an uncertain event time to a single fixed-width log bin when possible.

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": {
      "fruehestens_s": "<fruehestens_s>",
      "spaetestens_s": "<spaetestens_s>",
      "raster_s": "<raster_s>"
    },
    "name": "raumlogger_ereignis_raster_grenzfall"
  }
}

Input Schema

NameRequiredDescriptionDefault
raster_sYesKonstante Rasterbreite in Sekunden.
fruehestens_sYesFrühester möglicher Beginn, Sekunden ab Rasterursprung.
spaetestens_sYesSpätester möglicher Beginn, Sekunden ab Rasterursprung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 safety and locality are covered. The description adds a genuine decision rule (only assign when the position is unambiguous), but omits what the tool returns or raises in the ambiguous case and says nothing about whether bounds are inclusive or how ties at bin edges are resolved.

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 short clauses, front-loaded with the operative condition; the German/English duplication is redundant but harmless and keeps it bilingual. No filler.

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 small three-parameter read-only helper with no output schema, the definition covers the intent but not the outcome: what is returned when a unique bin exists versus when it does not (null, error, nearest bin) remains unspecified. That is the main gap an agent would hit at call time.

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 coverage is 100%, so fruehestens_s, spaetestens_s and raster_s are already documented. The description supplies the semantic framing — an uncertainty interval for a ventilation start projected onto a constant-width grid — which is a modest but real addition over the schema's mechanical min/max descriptions.

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 — assigning an imprecisely logged ventilation start time to exactly one fixed-width log bin — which resolves the cryptic tool name (Grenzfall/borderline case). It is distinguishable from a general binning tool by the 'nur bei eindeutiger Lage' qualifier, though it never names the sibling that handles unambiguous or non-assignable cases.

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?

The phrase 'nur bei eindeutiger Lage' / 'when possible' gives an implicit precondition for use, which is better than nothing. However, it never states what to do when the position is ambiguous, nor does it point to an alternative tool for that situation, leaving the agent to guess.

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