Skip to main content
Glama

getecoback-raumklima

balkonschatten_sitzplatzwechsel_stichproben

Read-only

Ermittelt den kleinsten Sitzwechselbedarf für drei bereits beobachtete Schattenzustände — Find the fewest seat changes across three sampled balcony shade states.

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": {
      "startplatz": "<startplatz>",
      "erste_probe": "<erste_probe>",
      "zweite_probe": "<zweite_probe>",
      "dritte_probe": "<dritte_probe>"
    },
    "name": "balkonschatten_sitzplatzwechsel_stichproben"
  }
}

Input Schema

NameRequiredDescriptionDefault
startplatzYesAktueller frei nutzbarer Sitzplatz.
erste_probeYesIm Schatten sichtbare Plätze in der ersten Stichprobe.
dritte_probeYesSchatten in der dritten Stichprobe.
zweite_probeYesSchatten in der zweiten Stichprobe.

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 adds the minimization semantics ('kleinsten'/'fewest'), which tells the agent this is an optimization over the three samples rather than a simple tally. It does not explain how missing/unknown samples are treated or whether an infeasible configuration is reported.

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?

One compact sentence, front-loaded with the verb and result, with a bilingual restatement that costs little. Nothing superfluous, though the English half is largely a mirror of the German half rather than adding information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Missing.

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% with enums on all four parameters, so the schema already explains 'startplatz' and the three probes. The description adds only the framing that all three probes are joint inputs to one minimization; it adds no meaning about how a probe value interacts with the starting seat. 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 and result ('Ermittelt den kleinsten Sitzwechselbedarf') over a named resource ('drei bereits beobachtete Schattenzustände'), so an agent can tell this is an optimization/computation tool rather than a lookup. It does not differentiate itself explicitly from sibling shade-estimation tools such as 'balkon_schattenkante_schaetzen', but the purpose itself is unambiguous.

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?

The phrase 'bereits beobachtete' implies a precondition that the three shade states have already been sampled, which is modestly useful. There is no statement of when to prefer this over other balcony/shade tools, no exclusions, and no explanation of when the 'unbekannt' or 'keiner' enum values are appropriate inputs.

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