Skip to main content
Glama

getecoback-climate-weather

klimafenster_stoffkit_schadensbild

Read-only

Reißverschluss, Stoff und Haltepunkte eines wiederverwendeten Fensterkits beurteilen — Identify which fabric window-kit component needs inspection before reuse.

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": {
      "verschluss": "<verschluss>",
      "loch_im_stoff": "<loch_im_stoff>",
      "rand_loest_sich": "<rand_loest_sich>"
    },
    "name": "klimafenster_stoffkit_schadensbild"
  }
}

Input Schema

NameRequiredDescriptionDefault
verschlussYesBeobachtung am Reißverschluss.
loch_im_stoffYesEin Riss oder Loch ist jenseits der vorgesehenen Schlauchöffnung sichtbar?
rand_loest_sichYesDer Stoff oder Halter löst sich am Rahmen?

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 covered. The description adds that the tool evaluates a previously used kit and that the result points to a component needing inspection, which hints at the return value despite no output schema; it does not explain how conflicting observations are resolved.

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 definition is two short clauses with the purpose front-loaded and no filler. The German/English duplication is slightly redundant but serves disambiguation rather than padding.

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 three-required-parameter read-only assessment with no output schema, the definition covers what the tool is about and roughly what it produces. It leaves open how the assessment combines the observations and how the 'unbekannt' enum case is treated, which an agent would want to know.

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 the enum values are documented in the schema, so the baseline of 3 applies. The description's enumeration of zipper, fabric and attachment points loosely maps to the three parameters but adds no format or interpretation detail 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 names a specific verb ('beurteilen' / 'identify') and a concrete resource (zipper, fabric and attachment points of a reusable window kit), so the agent knows this is an inspection-assessment tool. It does not differentiate itself from any named sibling, and the phrasing 'identify which component needs inspection' slightly conflicts with a schema that requires all three observations as input.

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 phrase 'before reuse' implies the situation in which the tool applies, which is useful context. However, there is no explicit when-to-use versus when-not, no mention of alternatives, and no statement of what to do if only one component is suspect.

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