Skip to main content
Glama

getecoback-raumklima

terrasse_schattenfolge_pause_ohne_platzwechsel

Read-only

Zwei beobachtete Schattenphasen am selben Tisch auf die längste zusammenhängende Nutzungszeit prüfen — Find the longest continuous shaded interval at one fixed table.

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_ab": "<a_ab>",
      "a_bis": "<a_bis>",
      "b_ab": "<b_ab>",
      "b_bis": "<b_bis>",
      "ziel_min": "<ziel_min>",
      "tisch_und_sonnenlage_gleich": "<tisch_und_sonnenlage_gleich>"
    },
    "name": "terrasse_schattenfolge_pause_ohne_platzwechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_abYesBeginn des ersten durchgehend beobachteten Schattenabschnitts.
b_abYesBeginn des zweiten Abschnitts.
a_bisYesEnde dieses Abschnitts.
b_bisYesEnde des zweiten Abschnitts.
ziel_minYesEigene gewünschte zusammenhängende Zeit.
tisch_und_sonnenlage_gleichYesSind beide Einträge am gleichen Tisch und für denselben Beobachtungstag?

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 the safety profile is covered. The description adds a real precondition (both phases must share table and observation day) but says nothing about the returned result, what happens when that boolean is false, or how ziel_min affects the outcome.

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 the core operation front-loaded. The German/English duplication is mildly redundant but serves disambiguation and earns its place reasonably well.

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 six required numeric/boolean parameters, no output schema, and only minimal annotations, the description should say what comes back (a merged interval? a yes/no against ziel_min?). The precondition is captured, but the result shape and the boolean's failure path are left unstated.

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 every parameter is already documented in the schema. The description contributes only the framing that a and b are merged and judged against the goal time; it does not clarify the role of ziel_min (threshold? comparison target?) or the failure behavior of tisch_und_sonnenlage_gleich.

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 names a concrete operation — checking two observed shade phases at one fixed table for the longest continuous usable interval — with a clear verb (prüfen) and subject. The phrase 'am selben Tisch' / 'one fixed table' implicitly distinguishes it from the platzwechsel siblings, but no sibling is named, so differentiation stays implicit.

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?

Usage is only implied through the required 'tisch_und_sonnenlage_gleich' precondition (both entries at the same table and observation day). There is no statement of when to pick this tool over the many other terrasse_* shade tools, nor what to do if the two phases are not from the same table.

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