Skip to main content
Glama

getecoback-climate-weather

backofenauszug_zwei_kalte_blickhoehen_ohne_umbau

Read-only

Bei zwei möglichen belegten Ebenen feststellen, ob alle nötigen Sichtpunkte ohne Positionswechsel erkennbar sind — Check alternative heights by uniquely visible required marks.

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": {
      "marken_gleich": "<marken_gleich>",
      "notwendig": "<notwendig>",
      "in_a": "<in_a>",
      "in_b": "<in_b>",
      "in_beiden": "<in_beiden>"
    },
    "name": "backofenauszug_zwei_kalte_blickhoehen_ohne_umbau"
  }
}

Input Schema

NameRequiredDescriptionDefault
in_aYesDavon in Position A ohne Wechsel tatsächlich lesbare Marken.
in_bYesDavon in Position B ohne Wechsel tatsächlich lesbare Marken.
in_beidenYesDavon eindeutig dieselben in beiden Stellungen sichtbaren Marken.
notwendigYesSichtmarken für einen vollständigen eigenen Kontrollschritt.
marken_gleichYesSind am kalten Aufbau in beiden betrachteten Stellungen dieselben erforderlichen Sichtmarken identifiziert?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description is consistent with that (it is a pure check), so no contradiction. But it adds nothing beyond the annotation: it does not say how the counts in_a/in_b/in_beiden are evaluated, what constitutes a failing result, or what the caller should do when marken_gleich is false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is only one sentence, so nothing is bloated, but the structure is poor: a German clause immediately followed by a quasi-English gloss that partially duplicates rather than front-loading the actionable rule. Every element could earn its place, yet the ordering makes the agent parse the same idea twice.

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 tool with five required parameters and no output schema, the description leaves key questions open: whether the result is a comparison of notwendig against in_a/in_b, how in_beiden resolves ties, and what happens on a negative outcome. Given the complexity of the check, substantially more behavioral explanation would be needed.

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 each parameter carries a precise German explanation, so the schema does the heavy lifting. The description contributes only the general notion of 'Sichtpunkte/Marken' and 'ohne Positionswechsel', which loosely frames but does not further constrain the five numeric/boolean inputs.

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 does state a determinate check: whether all required sight marks are identifiable at two possibly occupied levels without changing position. However, the phrasing is highly domain-specific jargon layered on an impenetrable German tool name, and the appended English gloss ('Check alternative heights by uniquely visible required marks') is a fragment rather than a clarifying restatement. It never distinguishes this check from the many similarly named backofenauszug_* siblings.

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 when-to-use statement, no condition under which to prefer this over e.g. backofenauszug_obere_untere_kalte_greifspur or the other height/mark tools, and no prerequisites or exclusions. The agent must infer from the name alone that this applies to the two-occupied-level 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