Skip to main content
Glama

getecoback-climate-weather

terrasse_sitzgruppe_schatten_kleinteile_freigabe

Read-only

Einen beobachteten Schattenplatz darauf prüfen, ob der kleine Tisch und die genutzten Sitzplätze gleichzeitig darin bleiben — Verify simultaneous shade for a group and tabletop, not successive coverage.

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": {
      "proben": "<proben>",
      "plaetze_im_schatten": "<plaetze_im_schatten>",
      "tisch_im_schatten": "<tisch_im_schatten>",
      "gleichzeitig": "<gleichzeitig>"
    },
    "name": "terrasse_sitzgruppe_schatten_kleinteile_freigabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
probenYesTerminbezogene Stichproben mit durchgehend gleicher Aufstellung.
gleichzeitigYesProben, in denen beides tatsächlich gleichzeitig im Schatten war.
tisch_im_schattenYesProben mit dem vorgesehenen Tischabschnitt im Schatten.
plaetze_im_schattenYesProben, in denen alle benutzten Plätze beschattet waren.

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 safety is covered; the description still contributes by framing the check as a simultaneity test over an observed placement rather than successive coverage. However, it never discloses what verdict is produced, what combination of the four counts constitutes a pass, or whether any threshold applies, which is the core behavior of this tool and is not covered by annotations or an output schema.

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 front-loaded sentence states the check first and the disambiguation last, with no filler. The bilingual German/English duplication is partly redundant, but for a German-named tool it serves as a disambiguation aid rather than padding.

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 four-required-parameter computational check with no output schema, the definition covers inputs adequately via the schema but leaves the outcome semantics open: how the counts combine into a result and what the caller receives back are unstated. It is minimally sufficient to invoke correctly, but not sufficient to interpret the result.

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 each of the four counts is already documented in the schema and the baseline of 3 applies. The description adds modest meaning by tying the counts to the simultaneity concept ('gleichzeitig'), but it does not explain the relationship among proben, tisch_im_schatten, plaetze_im_schatten and gleichzeitig beyond what the schema fields already state.

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 specific verb (prüfen/verify) and a specific resource (simultaneous shade over the small table plus the used seats), so the operation is identifiable despite the cryptic tool name. The clause 'not successive coverage' also separates it from sequence-oriented siblings such as terrasse_schattenfolge_pause_ohne_platzwechsel, though no sibling is named explicitly.

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: the agent can infer this is the check to run when simultaneity (rather than succession) matters, but there is no explicit 'use this when…' statement, no prerequisite, and no named alternative to route between. The contrast clause 'not successive coverage' is the only selection hint.

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