Skip to main content
Glama

getecoback-climate-weather

wohnmobil_messpunkt_nach_polsterrueckkehr_verdeckt

Read-only

Prüfe, ob der alte Vergleichspunkt nach dem Rückstellen des Polsters noch messbar ist — Audit whether an original measurement point remains accessible after restoring upholstery

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": {
      "markierung_sichtbar": "<markierung_sichtbar>",
      "alter_punkt_unverdeckt": "<alter_punkt_unverdeckt>",
      "neuer_punkt_gleichzeitig_gemessen": "<neuer_punkt_gleichzeitig_gemessen>"
    },
    "name": "wohnmobil_messpunkt_nach_polsterrueckkehr_verdeckt"
  }
}

Input Schema

NameRequiredDescriptionDefault
markierung_sichtbarYesUrsprüngliche Messpunktmarkierung ist nach Rückstellen erkennbar
alter_punkt_unverdecktYesDer ursprüngliche Punkt ist mit dem gleichen Verfahren ohne Verschieben des Polsters ablesbar
neuer_punkt_gleichzeitig_gemessenYesErsatzpunkt und Originalpunkt wurden vorher zeitgleich unter denselben Bedingungen beobachtet

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 and the description does not contradict it — 'prüfe' is consistent with a pure read/audit. Beyond that the description adds only the audit framing; it says nothing about what a negative verdict implies, whether the result is recorded anywhere, or how the three booleans combine into a conclusion.

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?

The core statement is short and front-loaded, which is good. However, the English half is a verbatim translation of the German rather than additional information, so the definition is effectively twice as long as its content warrants and the second sentence earns nothing new.

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 only three fully described boolean parameters, no output schema, and annotations covering the read-only nature, the definition is close to sufficient. What is missing is the decision logic: an agent cannot tell from the description whether all three must hold for the original point to count as still measurable, or how to report a partial 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%; all three booleans carry their own German descriptions, so the schema does the heavy lifting. The tool description adds no meaning about the parameters — notably it never explains the relationship between 'alter_punkt_unverdeckt' and the precondition 'neuer_punkt_gleichzeitig_gemessen', which is the non-obvious one.

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 names a concrete action ('Prüfe, ob ... noch messbar ist') and a concrete object ('alter Vergleichspunkt nach dem Rückstellen des Polsters'), so an agent knows this is a post-restoration accessibility audit rather than a measurement or marking tool. It does not, however, contrast itself with any of the many similarly named siblings (e.g. wohnmobil_rueckkehr_trockenkontrolle_materialpaar, wohnmobil_polster_vorne_hinten_seitenwechsel_befund), leaving disambiguation to the name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The trigger condition is embedded in the phrase 'nach dem Rückstellen des Polsters', which implies this is called only after upholstery has been put back. There is no explicit when-not guidance, no mention of prerequisites (e.g. that the substitute point must already have been observed), and no named alternative tool for the adjacent situations the siblings cover.

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