Skip to main content
Glama

getecoback-climate-weather

bad_fugenplan_abschnitte_nach_material_trennen

Read-only

Unbekannte und auffällige Fugenabschnitte aus einer bereits dokumentierten Pflegeroutine herausnehmen — Partition routine joint-care sections from unresolved materials and damage.

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": {
      "freigabe_geprueft": "<freigabe_geprueft>",
      "intakter_moertel": "<intakter_moertel>",
      "intaktes_silikon": "<intaktes_silikon>",
      "material_offen": "<material_offen>",
      "fuge_auffaellig": "<fuge_auffaellig>"
    },
    "name": "bad_fugenplan_abschnitte_nach_material_trennen"
  }
}

Input Schema

NameRequiredDescriptionDefault
material_offenYesWeitere Abschnitte mit unbekanntem Material.
fuge_auffaelligYesWeitere auffällige Abschnitte, deren Zustand zuerst begutachtet werden muss.
intakter_moertelYesBekannte intakte Mörtelabschnitte.
intaktes_silikonYesWeitere bekannte intakte Silikonabschnitte.
freigabe_geprueftYesIst die passende Pflegeroutine für die bereits identifizierten und intakten Abschnitte belegt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 input comes from an already documented routine, but leaves the 'herausnehmen'/'partition' ambiguity unresolved and says nothing about permissions, side effects, or result shape.

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 text is short, but it is a bilingual duplication of the same sentence in German and English, which pads the definition without adding information. The core scoping idea is present but not front-loaded clearly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a five-required-parameter, no-output-schema tool whose result format is never indicated (counts, grouped partitions, or list?). The required 'freigabe_geprueft' boolean acts as a precondition gate, yet the description never states that the release check must be satisfied before calling.

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 all five parameters are already documented in the schema, and the description adds no meaning beyond them. Baseline 3 applies when the schema carries the parameter burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a verb ('herausnehmen'/'partition') with a resource ('Fugenabschnitte'), but the phrasing is ambiguous: 'herausnehmen' literally reads as removal while the English gloss says 'partition', which implies classification. It also gives no differentiation from the many sibling tools that split or separate 'Abschnitte'.

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

Usage Guidelines2/5

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

There is a faint contextual hint that it operates on sections from an 'already documented care routine', but no explicit when-to-use condition, no exclusions, and no named alternative among the sibling tools. The agent must infer the trigger situation entirely.

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