Skip to main content
Glama

getecoback-raumklima

auto_parksonne_vorderseite_fensterseite_verschattung

Read-only

Prüfe, ob ein fester Schattenspender beide beobachteten Scheibenseiten während der Parkphase erreichte — Audit front and side shade across two phases of a parked vehicle

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": {
      "vorne_a": "<vorne_a>",
      "seite_a": "<seite_a>",
      "vorne_b": "<vorne_b>",
      "seite_b": "<seite_b>",
      "selber_parkplatz": "<selber_parkplatz>"
    },
    "name": "auto_parksonne_vorderseite_fensterseite_verschattung"
  }
}

Input Schema

NameRequiredDescriptionDefault
seite_aYesBetrachtete Seitenscheibe zu Beginn im Schatten
seite_bYesBetrachtete Seitenscheibe bei der späteren Stichprobe im Schatten
vorne_aYesFrontscheibenbereich zu Beginn im beobachteten Schatten
vorne_bYesFrontscheibenbereich bei der späteren Stichprobe im Schatten
selber_parkplatzYesUnveränderter Standplatz und unveränderte Ausrichtung

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 safety and locality are covered; the description correctly frames the tool as a pure evaluation ('Prüfe, ob ... erreichte'). It adds domain context that the comparison concerns one fixed shade source observed across two sampling points on a stationary vehicle, but says nothing about what the check returns or how conflicting observations between the two phases are treated.

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 with the subject ('fester Schattenspender') and scope ('Parkphase') stated before the bilingual restatement. The German and English halves are largely duplicative, which is mild padding, but overall it is tight and wastes no space on filler.

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 five fully documented required booleans, a read-only annotation and no output schema, the definition covers what to supply and that the call is side-effect free. What is missing is the decision logic: whether the tool reports per-window consistency, aggregates across both phases, or what conclusion an agent should draw from the returned verdict.

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 five booleans is already documented, setting the baseline at 3. The description reinforces the mapping of the _a/_b suffix pairs to the 'zwei Phasen' and confirms the shade source is fixed, but adds no interpretation of what a true/false combination means.

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 pairs a specific verb ('Prüfe' / 'Audit') with a concrete resource ('fester Schattenspender' reaching 'beide beobachteten Scheibenseiten' during the parked phase), and the two-phase framing ('vorne_a/seite_a' vs. 'vorne_b/seite_b') is stated outright. It does not name any sibling tool, so the agent must infer the boundary to tools like 'verschattung_erholung_innerhalb_eigener_streubreite' on its own.

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 explicit statement of when to use this tool versus an alternative, and no prerequisites or exclusions are given. The phrase 'während der Parkphase' is the only scoping hint, and it is embedded in the purpose clause rather than presented as usage guidance.

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