Skip to main content
Glama

getecoback-climate-weather

geraeteprogramm_je_freigabefenster_anzahlband

Read-only

Bei getrennten Gerätefunktionen unsichere Nutzungsdauer auf garantierte und mögliche gemeinsame Auftragszahl abbilden — Bound two-resource service capacity from documented availability intervals.

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": {
      "a_verfuegbar_min": "<a_verfuegbar_min>",
      "b_verfuegbar_min": "<b_verfuegbar_min>",
      "a_kurz_min": "<a_kurz_min>",
      "a_lang_min": "<a_lang_min>",
      "b_kurz_min": "<b_kurz_min>",
      "b_lang_min": "<b_lang_min>"
    },
    "name": "geraeteprogramm_je_freigabefenster_anzahlband"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_kurz_minYesUntere beobachtete Dauergrenze je Aufgabe auf A für diesen Ablauf.
a_lang_minYesObere entsprechend begründete Dauergrenze auf A.
b_kurz_minYesUntere Dauergrenze je Aufgabe auf B.
b_lang_minYesObere Dauergrenze je Aufgabe auf B.
a_verfuegbar_minYesBelegte nutzbare, zusammenhängende Dauer auf Gerät A.
b_verfuegbar_minYesBelegte entsprechende Dauer auf Gerät B.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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. The description does add real behavioral context beyond them: it operates on 'unsichere Nutzungsdauer' (uncertain durations) and converts them into a 'garantierte und mögliche' (guaranteed and possible) band, which tells the agent the result is an interval, not a point estimate. It does not disclose how ties, zero availability, or inconsistent short/long bounds are handled.

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 compact sentence with no filler, and the mechanism (uncertain duration -> band) leads before the English restatement. The bilingual duplication is arguably redundant, but it is the only thing making the cryptic German compound name interpretable, so it earns its space.

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?

All six required numeric parameters are fully documented in the schema and the read-only profile is covered by annotations, so input-side completeness is fine. However, with no output schema, the description should state what comes back (a guaranteed lower count and a possible upper count) and it never does, leaving the tool's actual product underspecified.

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%, so all six parameters (a/b_verfuegbar_min, a/b_kurz_min, a/b_lang_min) are already documented in the schema, and the description adds no parameter-level detail such as unit conventions or the required ordering kurz <= lang. Baseline 3 applies when the schema carries the parameter burden.

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 English gloss 'Bound two-resource service capacity from documented availability intervals' gives a verb (bound) and a resource (two-resource capacity), but the German half ('unsichere Nutzungsdauer auf garantierte und mögliche gemeinsame Auftragszahl abbilden') is dense domain jargon and the two halves do not quite line up. An agent can guess this computes a job-count band for two devices sharing a release window, but the phrasing never plainly states that the output is a guaranteed/possible count range. No sibling differentiation is offered.

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 use this tool, when not to, or which sibling to prefer for related device/window calculations. The only implicit guidance is the mention of 'getrennte Gerätefunktionen' (separate device functions), which hints at a precondition but is never spelled out as a usage rule.

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