Skip to main content
Glama

getecoback-raumklima

wohnmobil_staurouten_zwei_fachstellungen_nutzen

Read-only

Vergleiche, welche Stellung zweier Innenfächer bei der Saisonübernahme für die jeweilige Aufgabe beobachtet wurde — Map two camper cabinet positions to storage or access needs

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": {
      "gang_benoetigt_freien_durchgang": "<gang_benoetigt_freien_durchgang>",
      "fach_vorne": "<fach_vorne>",
      "fach_hinten": "<fach_hinten>",
      "fachstellung_markiert": "<fachstellung_markiert>"
    },
    "name": "wohnmobil_staurouten_zwei_fachstellungen_nutzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
fach_vorneYesZustand der vorderen Fachtür
fach_hintenYesZustand der hinteren Fachtür
fachstellung_markiertYesBeide Stellungen wurden für die aktuelle Aufgabe direkt kontrolliert
gang_benoetigt_freien_durchgangYesDer aktuelle Arbeitsschritt benötigt den vollen gemessenen Durchgang

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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, and the description is consistent with a pure observation/comparison with no side effects. Beyond that it adds little: it does not say what the comparison produces, how unknown states ("offen_unbekannt") are treated, or whether the result is a recommendation or a mere record.

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?

A single sentence, but the German/English doubling restates the same idea without adding information, and the phrasing is convoluted ("welche Stellung ... beobachtet wurde"). It is short but not front-loaded with the actionable verb-plus-result.

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?

For a read-only, four-boolean/enum-parameter tool whose schema is fully documented, the description alongside annotations is nearly sufficient to call it correctly. What is missing is the meaning of the return value (there is no output schema), but the input side is adequately covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with enums and per-field descriptions, so the baseline is 3, but the description contributes almost nothing beyond naming the two compartments that the schema already covers. It does not clarify the interaction between "gang_benoetigt_freien_durchgang" and the "offen_ragt_in_gang" enum values, nor what "fachstellung_markiert" implies for the comparison's validity.

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 German clause names a specific action ("Vergleiche, welche Stellung zweier Innenfächer ... beobachtet wurde") and the English gloss adds "Map two camper cabinet positions to storage or access needs", so the domain is identifiable. But the core operation stays abstract — is it recording, comparing, or classifying observed states? — and nothing distinguishes it from the many other camper-status siblings, so the purpose is only loosely pinned down.

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 situates the tool in a "Saisonübernahme" context, which implies when it applies, but it gives no explicit when-to-use versus when-not guidance and names no alternative tool. An agent must guess whether this is the right call versus the other Fachstellung/Polster siblings.

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