Skip to main content
Glama

getecoback-raumklima

monoblock_schlauch_sichtform_achsenvergleich

Read-only

Beschreibt das Achsenverhältnis an einer bereits vermessenen sichtbaren Stelle des unveränderten Schlauchs — Describe the axis ratio of a measured hose cross-section without inferring airflow.

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": {
      "a_mm": "<a_mm>",
      "b_mm": "<b_mm>",
      "referenz_a_mm": "<referenz_a_mm>",
      "referenz_b_mm": "<referenz_b_mm>",
      "massstab_geprueft": "<massstab_geprueft>"
    },
    "name": "monoblock_schlauch_sichtform_achsenvergleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_mmYesErste äußere Achse der Stelle im dokumentierten Zustand in mm.
b_mmYesSenkrechte zweite äußere Achse derselben Stelle in mm.
referenz_a_mmYesErste Achse an derselben Stelle in der vorhandenen Referenzaufnahme in mm.
referenz_b_mmYesSenkrechte zweite Achse in der Referenzaufnahme in mm.
massstab_geprueftYesGleicher Maßstab und Blickrichtung nachweisbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 safety is covered. The description adds useful scope context (no airflow inference, unchanged hose only) but never states what the massstab_geprueft gate does to the result or what the comparison yields when scales differ, which is the key behavioral question for this tool.

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?

Two short sentences, front-loaded with the core purpose; the bilingual restatement is redundant but does add a precise gloss ('without inferring airflow') for non-German readers. Nothing else is superfluous.

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 five-required-parameter read-only tool with no output schema, the description should indicate what comes back (a ratio? a deviation verdict?) and how the reference comparison is reported. It only says it 'describes the axis ratio', leaving the return value and the effect of a false scale check unstated.

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 (both current axes, both reference axes, and the scale-verified flag) are already fully documented. The description adds no additional meaning about how the axis pairs relate or how the reference comparison is computed; baseline 3 applies.

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?

States a specific verb and resource: describing the axis ratio at an already-measured visible location of the unchanged hose. The scope qualifiers ('bereits vermessen', 'unveränderten Schlauchs') distinguish it from measurement or interpolation tools, though no sibling is named explicitly.

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

Usage Guidelines4/5

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

The phrase 'an einer bereits vermessenen sichtbaren Stelle des unveränderten Schlauchs' sets a clear precondition (existing measurement, unmodified hose), and 'without inferring airflow' excludes a class of misuse. There is no explicit when-not or named alternative, so it falls short of a 5.

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