Skip to main content
Glama

getecoback-climate-weather

duschhalter_wandbelag_deckschicht_kontaktbeleg

Read-only

Bei einer Abdeckung zwischen bekanntem Untergrund und tatsächlich berührter Oberfläche unterscheiden — Track whether the visible face belongs to the documented substrate.

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": {
      "untergrund_belegt": "<untergrund_belegt>",
      "deckschicht": "<deckschicht>",
      "deckschicht_belegt": "<deckschicht_belegt>",
      "rand_oder_naht": "<rand_oder_naht>"
    },
    "name": "duschhalter_wandbelag_deckschicht_kontaktbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckschichtYesWas berührt das vorgesehene Kontaktfeld?
rand_oder_nahtYesEin Rand der Deckschicht oder eine Naht liegt im Kontaktfeld.
untergrund_belegtYesDer eigentliche Wanduntergrund ist dokumentiert.
deckschicht_belegtYesDie Herstellerunterlage bezieht sich ausdrücklich auf die tatsächlich berührte Deckschicht.

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 side effects and openness are covered. The description adds conceptual behavior—checking correspondence between the visible face and the documented substrate—but does not explain the result, thresholds, or how contact evidence is represented, leaving a gap because no output schema exists.

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?

The text is short and front-loads the scenario and purpose. The bilingual restatement is slightly redundant but still tight and readable.

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 four-required-parameter read-only check with full schema descriptions, the description is adequate to identify the tool's conceptual scope. It lacks return-value semantics (no output schema) and sibling routing, so an agent must infer how to interpret results and when to select this tool over related checks.

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%, so the four parameters and the enum are already fully documented. The description frames the overall relationship among substrate, covering, and touched surface but does not add syntax or value-specific meaning beyond the schema.

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 uses 'unterscheiden' and 'Track whether the visible face belongs to the documented substrate' to state a specific judgment about correspondence between the visible face and documented substrate when a covering exists. It is more than a restatement of the name and conveys the core decision, though it does not explicitly differentiate this tool from similar sibling checks.

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 opening 'Bei einer Abdeckung zwischen bekanntem Untergrund und tatsächlich berührter Oberfläche' implies the scenario in which the tool applies, but it never states when not to use it or names an alternative sibling. Guidance is therefore implied rather than explicit.

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