Skip to main content
Glama

getecoback-climate-weather

terrasse_polster_trocknung_naechste_sitzrunde

Read-only

Für ein eigenes Nutzungsfenster beobachtete verspätete Polster getrennt von passenden Ersatzplätzen zählen — Plan seating from verified cushion readiness and available replacements.

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": {
      "bestaetigt_trocken": "<bestaetigt_trocken>",
      "noch_offen": "<noch_offen>",
      "sitzplaetze_mit_ersatz": "<sitzplaetze_mit_ersatz>",
      "bedarf": "<bedarf>"
    },
    "name": "terrasse_polster_trocknung_naechste_sitzrunde"
  }
}

Input Schema

NameRequiredDescriptionDefault
bedarfYesFür die nächste Runde gewünschte nutzbare Plätze.
noch_offenYesAm selben Termin noch feuchte oder ungeprüfte Polster.
bestaetigt_trockenYesBis zum Termin vor Ort bestätigte trockene Polster.
sitzplaetze_mit_ersatzYesSeparat verifizierte nutzbare Ersatzplätze außerhalb der gezählten Polster.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/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 and the bar is lower. The description adds the notion that confirmed-dry and verified-substitute counts are combined, but says nothing about how they combine, what happens when demand exceeds supply, or what the computed result represents. The garbled opening clause further obscures rather than clarifies behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the structure is inverted: the first clause is an unintelligible German fragment and the actionable English purpose trails behind it. The German half does not earn its place because the schema and the English clause already carry the meaning.

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

Completeness2/5

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

There is no output schema, so the description must convey what the tool returns — a seat count, a shortfall, a plan? It never does. For a four-required-parameter computation tool with an unseen return shape, that is a material gap despite the fully documented inputs.

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 four numeric parameters are already documented in the schema with meaning and bounds. The description only echoes the concepts (dry readiness, replacements) without adding syntax, units, or interaction rules. Baseline 3 applies when the schema does the heavy lifting.

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 clause 'Plan seating from verified cushion readiness and available replacements' gives a verb (plan) and a resource (seating), which is roughly clear. But the leading German clause ('beobachtete verspätete Polster getrennt von passenden Ersatzplätzen zählen') is garbled and reads as a second, competing purpose, so the agent has to reconcile two framings. Nothing distinguishes it from the many other terrasse_* siblings in the catalog.

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 when-to-use or when-not-to-use guidance, and no alternative is named among the numerous sibling tools. The description implies a planning context but never states the situation that should select this tool over, for example, the other terrasse shadow/seating probes.

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