Skip to main content
Glama

getecoback-raumklima

ventilator_stellort_kabelweg_zwei_varianten

Read-only

Zwei bemaßte Kabelwege für einen geplanten Ventilatorstandort mit dem vorhandenen Kabel vergleichen — Compare measured route length and occupied-path conflicts at two fan locations.

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": {
      "nutzbare_laenge_cm": "<nutzbare_laenge_cm>",
      "a_weg_cm": "<a_weg_cm>",
      "b_weg_cm": "<b_weg_cm>",
      "eigene_wegreserve_cm": "<eigene_wegreserve_cm>",
      "a_kreuzt": "<a_kreuzt>",
      "b_kreuzt": "<b_kreuzt>"
    },
    "name": "ventilator_stellort_kabelweg_zwei_varianten"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_kreuztYesDer Weg an A würde eine regelmäßig benutzte Bodenpassage kreuzen?
a_weg_cmYesAn Position A am realen Verlauf gemessene Weglänge.
b_kreuztYesDer Weg an B würde eine regelmäßig benutzte Bodenpassage kreuzen?
b_weg_cmYesAn Position B gemessene Weglänge.
nutzbare_laenge_cmYesTatsächlich nutzbare Länge des Originalkabels oder USB-Kabels.
eigene_wegreserve_cmYesEigene zusätzliche Wegreserve, etwa für bereits gemessene Ecken.

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 agent knows this is a safe, local, side-effect-free computation. The description adds that occupied-path conflicts are part of the evaluation, which maps to the a_kreuzt/b_kreuzt booleans, but it never says how length versus conflict is weighed or whether the result is a recommendation or raw comparison data.

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?

A single front-loaded sentence with the core action first. The German and English halves largely restate each other, which adds length without new information, but the description remains short and free of 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?

With six required parameters and no output schema, the description should clarify what the comparison yields (a verdict, a delta, a recommendation) and how the usable cable length acts as a constraint. The decision logic and return shape are left implicit, which is a real gap for a six-input computation tool.

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 six parameters are already explained in the schema, making 3 the baseline. The description adds only a conceptual link, framing the measured distances plus crossing flags as 'route length and occupied-path conflicts', and says nothing about how nutzbare_laenge_cm or eigene_wegreserve_cm interact with the route measurements.

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 (vergleichen/compare) and resource (zwei bemaßte Kabelwege für einen geplanten Ventilatorstandort) and names the two criteria being compared, route length and passage conflicts. An agent knows exactly what operation this performs, though it does not differentiate itself from any sibling by name.

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 'für einen geplanten Ventilatorstandort mit dem vorhandenen Kabel' implies the scenario (fan placement planning with an existing cable) but gives no explicit when-to-use, when-not, or named alternative such as ventilator_platzbedarf_pruefen. Usage must be inferred from context rather than stated.

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