Skip to main content
Glama

getecoback-raumklima

camper_stellplatzwechsel_vorher_nachher_quellenscope

Read-only

Unterscheide einen dokumentierten Stellplatzwechsel von einem gleichzeitig umgeräumten Innenraum — Scope an observed camper change when placement and contents change together

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": {
      "standort_alt": "<standort_alt>",
      "standort_neu": "<standort_neu>",
      "polster_und_fachstellung_gleich": "<polster_und_fachstellung_gleich>",
      "vergleichbare_witterung": "<vergleichbare_witterung>"
    },
    "name": "camper_stellplatzwechsel_vorher_nachher_quellenscope"
  }
}

Input Schema

NameRequiredDescriptionDefault
standort_altYesBeobachtete vorige Umgebung
standort_neuYesSpätere beobachtete Umgebung
vergleichbare_witterungYesDie dokumentierten Beobachtungsfenster hatten ähnliche Witterung
polster_und_fachstellung_gleichYesTextilien und Fächer unverändert

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/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. The description adds no behavioral context beyond that — no statement of what is returned, how ties or ambiguous observations are handled, or what 'scope' means operationally. It restates the purpose in two languages rather than disclosing behavior.

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

Conciseness3/5

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

Two short clauses, front-loaded with the German statement, but the English half largely restates the German rather than adding information. There is no wasted length, yet the duplication means neither sentence earns full weight.

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?

Four required parameters, two enums, no output schema, and the description never indicates what the call returns or how the four inputs combine into a verdict. For a decision/classification tool with no output schema, the description should explain the result shape and the meaning of 'scope'; it does not.

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 two enumerated fields and two booleans, so the schema carries the parameter semantics and baseline 3 applies. The description gestures at the placement/contents distinction, which loosely maps to standort_* versus polster_und_fachstellung_gleich, but adds no interpretation of the enum values or of vergleichbare_witterung.

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?

"Unterscheide einen dokumentierten Stellplatzwechsel von einem gleichzeitig umgeräumten Innenraum" names a discriminating task over a camper placement change, but never states what the tool actually produces (a classification, a boolean verdict, a scoped record). The name and description are opaque enough that an agent cannot confidently distinguish it from siblings like camper_granulat_stellvergleich_spitzen_und_mittelwert.

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 description implies the decision the tool supports but gives no when-to-use condition, no exclusions, and no pointer to an alternative for the case where placement and contents changed independently. The agent must infer the invocation context entirely from the parameter names.

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