Skip to main content
Glama

getecoback-raumklima

abluftgitter_freien_querschnitt_lesen

Read-only

Anlagefläche und freien Querschnitt eines Gitters gegenüberstellen — Estimate net open area from a documented open-area ratio.

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": {
      "breite_cm": "<breite_cm>",
      "hoehe_cm": "<hoehe_cm>",
      "offen_prozent": "<offen_prozent>",
      "gefordert_cm2": "<gefordert_cm2>"
    },
    "name": "abluftgitter_freien_querschnitt_lesen"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoehe_cmYesHöhe derselben Bezugsfläche.
breite_cmYesBreite der als Bezug angegebenen rechteckigen Gitterfläche.
gefordert_cm2YesVom Geräteanbieter dokumentierte Mindestfläche in cm²; 0 wenn unbekannt.
offen_prozentYesDokumentierter freier Flächenanteil des Gitters in Prozent.

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 safety is covered. The description adds one useful behavioral point — the result is an *estimate* derived from a documented ratio rather than a measurement — which flags its non-authoritative nature. It stops short of saying how the comparison is reported (verdict vs. raw cm²) or what happens when the required area is unknown (0).

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 clauses, front-loaded with the core comparison and then the estimation intent. The English half largely restates the German half rather than extending it, which is minor waste, but nothing is buried or verbose.

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?

All four required parameters are fully documented and there is no output schema, yet the description never indicates what comes back (a computed open area, a pass/fail against gefordert_cm2, or both). For a small read-only calculation tool that is a noticeable but not severe gap.

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 of the four parameters carries a precise German description including the '0 wenn unbekannt' convention for gefordert_cm2. The description adds essentially no additional parameter meaning beyond restating the concept of a documented open-area ratio, so the 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 operation on a specific resource: comparing a grille's face area ('Anlagefläche') with its free cross-section and estimating net open area from a documented open-area ratio. The verb+resource pairing is unambiguous enough that an agent knows this is a geometric/airflow estimation, not a lookup. It does not, however, differentiate itself from the many sibling tools that also deal with exhaust-grille or airflow checks.

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 only implied by the parameter set — supply width, height, documented percent-open and a required minimum area to get a comparison. There is no explicit statement of when to call this versus related checks such as coupling alignment or hole-position verification, and no prerequisites or exclusions are given. An agent can infer the scenario but must guess at boundaries.

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