Skip to main content
Glama

getecoback-climate-weather

led_flimmermass_pstlm_svm_dimmlage_beleg

Read-only

PstLM und SVM auf die richtige Art der Zeitlichtbeobachtung und die tatsächlich dokumentierte Dimmlage begrenzen — Keep distinct temporal-light metrics tied to their declared operating state.

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": {
      "messwert": "<messwert>",
      "entscheidung": "<entscheidung>",
      "beleg_stufe": "<beleg_stufe>",
      "anfrage_stufe": "<anfrage_stufe>",
      "modell_und_zustand_bestaetigt": "<modell_und_zustand_bestaetigt>"
    },
    "name": "led_flimmermass_pstlm_svm_dimmlage_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
messwertYesWelcher ausdrücklich bezeichnete Kennwert liegt vor?
beleg_stufeYesDokumentierte Betriebsstufe, auf die sich der Kennwert bezieht.
entscheidungYesWelcher Aspekt soll gelesen werden?
anfrage_stufeYesTatsächlich interessierende Stufe.
modell_und_zustand_bestaetigtYesModell und Betriebsstufe sind für die konkrete Angabe geprüft?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 is not required to restate it. What it adds is the constraint that metrics stay tied to their declared operating state, implying mismatch handling between `beleg_stufe` and `anfrage_stufe`. It does not say what happens on mismatch (rejection, flagging, or silent pass), which is the behavior an agent most needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the two metrics, which is good, but the same proposition is stated twice, once in German and once in English, so half the text is redundant. The em-dash construction is also cryptic rather than clarifying.

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?

Five required parameters and no output schema, so the agent gets no picture of the result (pass/fail, adjusted classification, or echo of inputs). The enums are fully documented, which limits the damage, but a validation-style tool needs at least a hint of what it returns and how `modell_und_zustand_bestaetigt=false` is treated.

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 four parameters carry enums with German descriptions, so the schema does the heavy lifting. The description reinforces the metric-to-operating-state relationship but adds no field-level detail beyond what the enum labels already convey (e.g. what 'offen' means in practice).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the two concrete metrics (PstLM, SVM) and the concept of a documented dimming level, which maps onto the `entscheidung` and `beleg_stufe` enums. But the operative verb is abstract ('begrenzen' / 'keep tied to'), and neither sentence says whether the tool checks, records, or returns a corrected classification. An agent can guess the domain but not the operation.

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 call this versus the many sibling 'beleg' tools, no preconditions, and no exclusions. The only hint is implicit: it applies when a temporal-light metric (PstLM/SVM) has to be matched to a declared operating stage. The agent must infer the trigger entirely.

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