Skip to main content
Glama

getecoback-climate-weather

stellwand_freie_abschnitte_ermitteln

Read-only

Längsten zusammenhängenden freien Wandabschnitt trotz zwei Hindernissen finden — Find the longest clear wall span rather than adding separated gaps.

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": {
      "wand_cm": "<wand_cm>",
      "a_start_cm": "<a_start_cm>",
      "a_ende_cm": "<a_ende_cm>",
      "b_start_cm": "<b_start_cm>",
      "b_ende_cm": "<b_ende_cm>"
    },
    "name": "stellwand_freie_abschnitte_ermitteln"
  }
}

Input Schema

NameRequiredDescriptionDefault
wand_cmYesWandbreite entlang einer Skizzenachse.
a_ende_cmYesRechte Kante des ersten blockierten Abschnitts.
b_ende_cmYesRechte Kante des zweiten blockierten Abschnitts.
a_start_cmYesLinke Kante des ersten blockierten Abschnitts ab Wandanfang.
b_start_cmYesLinke Kante des zweiten blockierten Abschnitts.

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 establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description only needs to add computational behavior. It does add the key semantic that the result is one contiguous span rather than summed gaps, but it says nothing about how overlapping or out-of-order obstacle intervals are handled, nor what the return value looks like even though no output schema exists.

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 outcome and followed by the disambiguating contrast. The bilingual restatement of the same sentence is slightly redundant but still compact and readable.

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 pure geometric computation with five required numeric parameters and no output schema, an agent still needs to know what comes back (span length only, or length plus start/end offsets) and how degenerate cases—overlapping obstacles, zero-width spans, obstacles touching the wall ends—are treated. The description covers the core intent but leaves those gaps.

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%, and the schema already labels Wandbreite plus the left/right edges of both blocked sections in German. The description adds no syntax, units, or ordering constraints beyond that, so the baseline 3 for schema-covered parameters is appropriate.

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 names a concrete verb and output ('Längsten zusammenhängenden freien Wandabschnitt ... finden') and bounds the scenario to exactly two obstacles. It further distinguishes itself from an alternative interpretation by saying it returns the longest contiguous span 'rather than adding separated gaps', though it never names a sibling tool, so the differentiation is conceptual rather than routing-level.

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?

Usage is implied by the framing 'trotz zwei Hindernissen' and by the contrast with 'adding separated gaps', which tells the agent this is not a summing/concatenation tool. However, there is no explicit when-to-use clause, no mention of prerequisites such as ordering constraints on the start/end pairs, and no named alternative for the summing case.

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