Skip to main content
Glama

getecoback-raumklima

textil_nahtbereit_gegen_falte_umlegen

Read-only

Beim Umlegen eines bereits kontrollierten Stücks nicht erneut belegte Prüfpunkte erkennen — Keep track of textile checks whose accessibility changed after refolding.

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": {
      "punkte_identifiziert": "<punkte_identifiziert>",
      "sichtpunkte": "<sichtpunkte>",
      "schon_kontrolliert": "<schon_kontrolliert>",
      "danach_verdeckt": "<danach_verdeckt>",
      "davon_schon_kontrolliert": "<davon_schon_kontrolliert>"
    },
    "name": "textil_nahtbereit_gegen_falte_umlegen"
  }
}

Input Schema

NameRequiredDescriptionDefault
sichtpunkteYesInsgesamt vorgesehene Prüfpunkte.
danach_verdecktYesNach dem Umlegen verdeckte Punkte.
schon_kontrolliertYesVor dem Umlegen bereits kontrollierte Punkte.
punkte_identifiziertYesSind dieselben Stellen vor und nach dem Umlegen eindeutig identifiziert?
davon_schon_kontrolliertYesSchnittmenge der verdeckten und bereits kontrollierten Punkte.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations readOnlyHint=true and openWorldHint=false already establish that this is a safe read-only operation. The description adds that accessibility changes after refolding matter, but it does not explain return values, how punkte_identifiziert=false is handled, or what 'keep track' means operationally.

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 one short sentence with no wasted padding, and the refolding context is front-loaded. The German and English halves duplicate the same idea, but the text remains concise.

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?

For a five-required-parameter read-only tool with no output schema, the description is too thin: it does not say what the tool returns or how to interpret the five inputs. An agent still lacks essential information about the tool's output and decision behavior.

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 coverage is 100%, so the parameter descriptions already carry the semantic load. The description adds only a broad access-change concept and does not clarify the required counts or the boolean flag beyond the schema.

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 names a domain action ('keep track of textile checks whose accessibility changed after refolding') and gives a refolding context, but it does not state the concrete operation or result, such as computing which hidden points still need checking. It remains vague and does not clearly distinguish this tool from sibling textile tools.

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 phrase 'Beim Umlegen eines bereits kontrollierten Stücks' supplies a usage context, but there is no explicit when-not guidance, prerequisites, or alternative tool. The when-to-use guidance is implied rather than clear.

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