Skip to main content
Glama

getecoback-climate-weather

campereinwinterung_innenzonen_pruefstatus

Read-only

Ordne zugängliche und verdeckte Zonen des abgestellten Campers nach ihrem tatsächlichen Sichtbefund — Triage accessible and hidden camper zones from the actual inspection

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": {
      "fensterrahmen": "<fensterrahmen>",
      "polsterruecken": "<polsterruecken>",
      "staukasten": "<staukasten>"
    },
    "name": "campereinwinterung_innenzonen_pruefstatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
staukastenYesBefund in der tiefen Zone des Staukastens
fensterrahmenYesBefund am Fensterrahmen
polsterrueckenYesBefund auf der verdeckten Rückseite des Polsters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 the safety profile is covered. The description adds that findings must reflect the "tatsächlichen Sichtbefund" (actual visual observation) and that zones may be accessible or hidden, which constrains how inputs should be filled. It does not say what the operation produces — a classification, a list, or an ordering — leaving the behavioral outcome undisclosed.

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?

It is a single front-loaded sentence with the verb first and no filler. The German and English halves restate the same content, which is a small redundancy but keeps the definition short and scannable.

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 three required enum parameters and no output schema, the description should clarify what result the triage returns and how the mixed states such as 'nicht_zugaenglich' and 'noch_nicht_geprueft' affect the outcome. It conveys the inspection premise but leaves the return semantics and the decision rule unstated.

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%: all three parameters have enum values and descriptions, including the deep storage-box zone, window frame, and hidden cushion back. The description's phrase "zugängliche und verdeckte Zonen" loosely echoes those zones but adds no enum meaning, measurement criteria, or format detail beyond the schema. Baseline 3 applies.

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 description names a resource (accessible and hidden zones of the parked camper) and an action ("Ordne ... nach ihrem tatsächlichen Sichtbefund" / "Triage"), but the verb is abstract: it is unclear whether the tool records findings, sorts them, or derives a status. It gives no differentiation against the many sibling inspection tools, so an agent must infer the tool's exact role from the name and schema.

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 when-to-use guidance, no preconditions, and no named alternative. The phrase "abgestellter Camper" implies the context (a parked/winterized camper) but nothing states when this triage step is appropriate versus another inspection sibling.

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