Skip to main content
Glama

getecoback-climate-weather

schalllog_spitze_zu_abschnittsgrenze

Read-only

Ordnet eine aufgezeichnete Spitze einer normalen Betriebsphase oder einer unsicheren Grenze zu — Assign an observed peak to a logged phase while preserving boundary ambiguity.

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": {
      "spitze_sek": "<spitze_sek>",
      "phasenwechsel_sek": "<phasenwechsel_sek>",
      "zeitunsicherheit_sek": "<zeitunsicherheit_sek>"
    },
    "name": "schalllog_spitze_zu_abschnittsgrenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
spitze_sekYesZeitstempel der Spitze ab Protokollbeginn in Sekunden.
phasenwechsel_sekYesZeitstempel des beobachteten Gerätephasenwechsels in Sekunden.
zeitunsicherheit_sekYesGrößte angenommene Gesamtabweichung beider Zeitmarken in Sekunden.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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. The description does add one genuinely useful behavioral trait beyond that — that boundary ambiguity is preserved rather than resolved — but it says nothing about how ambiguity is signalled in the result or what thresholds trigger the uncertain case.

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 front-loaded sentences that lead with the assignment operation before adding the ambiguity-preservation caveat. The bilingual duplication is mildly redundant but aids disambiguation and costs little.

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 no output schema, the description should clarify what the assignment returns — a phase label, an ambiguous marker, or both. The phrase 'preserving boundary ambiguity' hints at a tri-state outcome but never states it, leaving the return shape to inference for a classification-type tool.

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%: all three timing parameters (peak timestamp, phase-change timestamp, total time uncertainty) are documented in the schema with units and bounds. The description adds no syntax or interpretation beyond that, so the baseline 3 applies.

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?

States a specific verb (assign/'ordnet zu') and specific resources: an observed peak onto a normal operating phase or an uncertain boundary. That is enough for an agent to distinguish it from sibling peak-matching tools such as geraeteton_schmalband_spitze_gegen_nachbarbaender, though the description never names an alternative explicitly.

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

Usage Guidelines2/5

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

There is no statement of when to choose this tool over the sibling peak-assignment tools, no preconditions, and no exclusions. The only guidance is implicit in the verb 'assign', which an agent must infer.

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