Skip to main content
Glama

getecoback-climate-weather

pflege_stellflaeche_schutzauflage_abnehmen

Read-only

Bei einer geschützten Arbeitsfläche die Nachkontrolle nach tatsächlicher Abnahme der Auflage erfassen — Check the hand-back state after a protective sheet is removed.

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": {
      "verwendung_belegt": "<verwendung_belegt>",
      "auflage_abgenommen": "<auflage_abgenommen>",
      "flaeche_oben_gecheckt": "<flaeche_oben_gecheckt>",
      "kante_gecheckt": "<kante_gecheckt>",
      "auffaellig": "<auffaellig>"
    },
    "name": "pflege_stellflaeche_schutzauflage_abnehmen"
  }
}

Input Schema

NameRequiredDescriptionDefault
auffaelligYesWurde nach der Abnahme eine Abweichung wie Restfeuchte oder Rückstand beobachtet?
kante_gechecktYesIst die tatsächlich berührte Kante nach Abnahme geprüft?
verwendung_belegtYesIst die Auflage bei dieser Arbeit zulässig und ist der vorgesehene Abschluss der Fläche bekannt?
auflage_abgenommenYesIst die Auflage vollständig separat weggelegt?
flaeche_oben_gechecktYesIst die Fläche unter der Auflage nach Abnahme geprüft?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 carried by structured data. The description adds which state is being inspected (the hand-back state of the surface and edge) but does not say what happens when a parameter such as auffaellig is true, whether a negative answer blocks the workflow, or whether any result is persisted — a slight tension with 'erfassen' under a read-only hint.

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 short clauses, front-loaded with the situation before the action, with no filler. The German and English halves are largely duplicative, which costs a little space but aids comprehension.

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?

For a five-required-boolean gate tool with no output schema, the definition says what is being checked but not how the five answers combine, what a pass versus a flagged deviation means, or what the caller receives. Annotations cover the read-only profile, so the remaining gap is about outcome semantics rather than safety.

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 all five booleans individually documented in German, so the schema already carries the parameter meaning. The description frames the whole set as a hand-back state check but adds no per-parameter interpretation, ordering, or consequence information beyond that framing.

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 situation (a protected working surface after a protective sheet has actually been removed) and a concrete action (capturing the follow-up check / hand-back state). It is distinguishable from removal-type siblings because it explicitly says the removal has already happened and this is the Nachkontrolle. The verb 'erfassen' is slightly soft compared with a precise verb like 'prüfen' or 'bestätigen'.

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?

Timing is implied by 'nach tatsächlicher Abnahme der Auflage', so an agent can infer this is the post-removal step rather than the removal itself. There is no explicit statement about when not to use it, no mention of prerequisite steps, and no routing to any alternative tool among the many similarly named pflege_* 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