Skip to main content
Glama

getecoback-raumklima

dachfenster_kit_randskizze_offene_abschnitte

Read-only

Addiert sichtbar unbedeckte, getrennte Abschnitte am ruhenden Rand eines vorhandenen Stoffkits — Total visible nonoverlapping gaps in a stationary roof-window seal.

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": {
      "oben_mm": "<oben_mm>",
      "links_mm": "<links_mm>",
      "rechts_mm": "<rechts_mm>",
      "komplett_einsehbar": "<komplett_einsehbar>"
    },
    "name": "dachfenster_kit_randskizze_offene_abschnitte"
  }
}

Input Schema

NameRequiredDescriptionDefault
oben_mmYesUnbedeckter Randabschnitt oben in mm.
links_mmYesUnbedeckter Randabschnitt links ohne Ecküberlappung in mm.
rechts_mmYesUnbedeckter Randabschnitt rechts ohne Ecküberlappung in mm.
komplett_einsehbarYesAlle drei Abschnitte waren vollständig von innen sichtbar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The read-only and closed-world annotations already establish that this is a safe computation. The description adds domain behavior by limiting the calculation to visible, separate, nonoverlapping gaps at a resting edge, but it does not explain result format, units, rounding, or handling of edge cases beyond what the schema implies.

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 compact and front-loads the operation and scope in a single sentence. The German-English bilingual phrasing is slightly redundant but not wasteful enough to obscure the purpose.

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-parameter calculation tool with no output schema, the description states what is totaled but does not specify the return value's format or units. The input schema is fully documented, and the read-only annotation covers safety, so the definition is adequate but leaves output semantics partly inferred.

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 parameter meanings are already well documented in the input schema. The description reinforces that the gaps are visible and nonoverlapping, but adds no syntax, units, or parameter-level 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 gives a specific verb and resource: it sums visibly uncovered, separate sections along the resting edge of an existing fabric kit. The English gloss clarifies that it returns total nonoverlapping gaps, though it does not explicitly distinguish this from related sibling tools such as individual edge-reserve tools.

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 no explicit guidance on when to use this tool versus alternatives, nor any stated preconditions beyond the reference to an existing fabric kit. The context implies it applies to a stationary roof-window seal, but the agent must infer when this tool is the right choice.

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