Skip to main content
Glama

getecoback-raumklima

fensterplatte_auflage_eckkontakt_sichtkarte

Read-only

Trennt sichtbare Auflageunterbrechungen und verdeckte Ecken einer vorhandenen Fensterplatte — Locate visible gaps in currently observed corner contact.

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_links": "<oben_links>",
      "oben_rechts": "<oben_rechts>",
      "unten_links": "<unten_links>",
      "unten_rechts": "<unten_rechts>"
    },
    "name": "fensterplatte_auflage_eckkontakt_sichtkarte"
  }
}

Input Schema

NameRequiredDescriptionDefault
oben_linksYesSichtbefund oben links.
oben_rechtsYesSichtbefund oben rechts.
unten_linksYesSichtbefund unten links.
unten_rechtsYesSichtbefund unten rechts.

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 readOnlyHint and openWorldHint annotations already establish that this is a safe, closed-world read operation, and the description does not contradict them. It adds only that the assessment concerns visible gaps and hidden corners of an existing plate, without further detail on outputs or limitations.

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 description is short and front-loads the core operation. The German and English forms partly repeat each other, but the wording remains efficient and does not 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 simple four-parameter read-only classification tool, the fully described enum schema and annotations cover much of what an agent needs. However, with no output schema, the description does not explain what the resulting 'Sichtkarte' contains or how the visible and hidden findings are reported.

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%, with each of the four required enum parameters documented as a visual finding for a specific corner. The description hints at visible versus hidden states through 'sichtbare' and 'verdeckte', but adds little beyond the already clear 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 names a specific domain action: separating visible support interruptions and hidden corners on an existing window plate. It is understandable apart from generic tools, though it does not explicitly distinguish itself from the many adjacent fensterplatte 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?

It gives no when-to-use or when-not-to-use guidance, and it names no alternatives among the sibling tools. The phrase 'currently observed corner contact' implies an inspection context, but that is not developed into routing guidance.

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