Skip to main content
Glama

getecoback-climate-weather

pflege_nutzungswechsel_beschriftung_sichtprobe

Read-only

Nach einem Wechsel des gemeinsam genutzten Pflegeplatzes die Lesbarkeit der vorhandenen Kennzeichnung prüfen — Check label readability from the actual approach and working position.

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": {
      "gleiche_markierung": "<gleiche_markierung>",
      "zugang_alt": "<zugang_alt>",
      "arbeit_alt": "<arbeit_alt>",
      "zugang_neu": "<zugang_neu>",
      "arbeit_neu": "<arbeit_neu>"
    },
    "name": "pflege_nutzungswechsel_beschriftung_sichtprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
arbeit_altYesWar sie am alten Platz während der üblichen Handgriffe sichtbar?
arbeit_neuYesIst sie am neuen Platz während der üblichen Handgriffe sichtbar?
zugang_altYesWar die Kennzeichnung am alten Platz beim Herangehen aus normaler Position eindeutig lesbar?
zugang_neuYesIst sie am neuen Platz beim Herangehen lesbar?
gleiche_markierungYesWurde an beiden Plätzen dieselbe Kennzeichnung auf derselben Fläche unter den üblichen Bedingungen verglichen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 real behavioral value by fixing the inspection stance ('aus der tatsächlichen Herangehens- und Arbeitsposition'), but it says nothing about how the boolean findings are recorded or what a failed check implies downstream.

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?

Two compact clauses with the trigger front-loaded. The English half is a straight translation rather than new information, which is a mild redundancy but useful for non-German readers and adds no bloat otherwise.

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, closed-world five-boolean inspection with full schema coverage and no output schema, the description supplies purpose, trigger and inspection stance. The only omission is what the caller should do with an unreadable finding, which is arguably outside this tool's scope.

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%, and each of the five required booleans carries its own question in the schema, so the schema does the semantic work. The description adds no further interpretation of gleiche_markierung, zugang_alt/neu or arbeit_alt/neu beyond what is already documented.

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 specific verb (Lesbarkeit prüfen / check readability) and a specific resource (die vorhandene Kennzeichnung) bound to a concrete trigger (nach einem Wechsel des gemeinsam genutzten Pflegeplatzes). An agent can tell this is a post-relocation label inspection rather than a generic care task, though no sibling is named or ruled out.

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

Usage Guidelines4/5

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

The when is embedded in the first clause: use this after a shared care place has changed. It does not state when not to use it or point to any alternative, so the context is clear but the routing is left to the caller.

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