Skip to main content
Glama

getecoback-raumklima

strommessgeraet_ausleihe_zwei_terminpaare_stabil

Read-only

Bei zwei gleitenden Ausleihfenstern prüfen, ob beide unteilbaren Messabschnitte bei einer zulässigen Rückgabe in mindestens einer Reihenfolge passen — Check both complete meter-loan orders with separate booking windows and a verified return gap.

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_frueh_min": "<a_frueh_min>",
      "a_spaet_min": "<a_spaet_min>",
      "a_dauer_min": "<a_dauer_min>",
      "b_frueh_min": "<b_frueh_min>",
      "b_spaet_min": "<b_spaet_min>",
      "b_dauer_min": "<b_dauer_min>",
      "rueckgabe_min": "<rueckgabe_min>"
    },
    "name": "strommessgeraet_ausleihe_zwei_terminpaare_stabil"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_dauer_minYesDauer des unteilbaren Abschnitts A.
a_frueh_minYesFrühester Start des vollständigen Abschnitts A ab Zeitachsenbeginn.
a_spaet_minYesSpätester laut Absprache noch passender Start des Abschnitts A.
b_dauer_minYesDauer des unteilbaren Abschnitts B.
b_frueh_minYesFrühester Start des vollständigen Abschnitts B.
b_spaet_minYesSpätester passender Start des Abschnitts B.
rueckgabe_minYesBenötigte bestätigte Zeit der Übernahme in beiden Richtungen.

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 declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description usefully adds that the check is existential over orderings ('in mindestens einer Reihenfolge') and depends on a permissible return gap, but it does not disclose the return value or what happens when no ordering fits.

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?

It is a single front-loaded sentence with no filler, and the core feasibility condition is stated immediately. The German/English duplication is somewhat redundant but compact and does not obscure the meaning.

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 seven-parameter computational feasibility tool with no output schema, the description explains the logical condition but omits what the tool actually returns (e.g. boolean feasibility, an ordering, or a schedule). That is a meaningful gap, though the annotations and fully described schema cover much of the operational context.

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 seven parameters are already documented in the input schema. The description conceptually maps the two windows, two indivisible sections and return gap, but adds no syntax, units, or parameter-level meaning 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 states a specific verb ('prüfen/check') and a precise resource: whether both indivisible meter-loan sections fit across two sliding booking windows given a verified return gap. It is far more specific than a tautology and an agent can understand the feasibility-check nature, though it does not explicitly differentiate itself from the many sibling scheduling tools.

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 scenario implies when to use it: when two complete meter-loan segments with separate windows need a feasibility check. However, there is no explicit when-not guidance, no prerequisites, and no named alternative among the extensive sibling catalog.

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