Skip to main content
Glama

getecoback-raumklima

saugwischer_freigegebene_abschnitte_flaechenbilanz

Read-only

Gemessene Wohnfläche nach abschnittsweise dokumentierter Bodenfreigabe aufteilen — Sum eligible, excluded and unresolved floor areas separately.

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": {
      "abschnitt_a": "<abschnitt_a>",
      "a": "<a>",
      "abschnitt_b": "<abschnitt_b>",
      "b": "<b>",
      "abschnitt_c": "<abschnitt_c>",
      "c": "<c>"
    },
    "name": "saugwischer_freigegebene_abschnitte_flaechenbilanz"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesStatus Abschnitt A.
bYesStatus Abschnitt B.
cYesStatus Abschnitt C.
abschnitt_aYesFläche von Abschnitt A in m².
abschnitt_bYesFläche von Abschnitt B in m².
abschnitt_cYesFläche von Abschnitt C in m².

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered, and the description correctly frames this as a pure aggregation. It does not disclose the result structure (three totals, their names or ordering), which matters because 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.

Conciseness3/5

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

It is a single short sentence, which is appropriately sized, but it says the same thing twice in two languages ('aufteilen' then 'Sum ... separately'), so a portion of the text is redundant rather than additive.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple six-parameter aggregation with complete schema documentation and read-only annotations, the definition conveys enough to call the tool correctly: three section areas plus three statuses, grouped into eligible/excluded/unresolved totals. Only the exact response shape is left unstated, and that is a minor gap given the tool's simplicity.

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 coverage is 100%: each parameter is documented with unit (m²), range (0–500) and the three status enum values. The description only implicitly maps freigegeben/ausgeschlossen/offen onto eligible/excluded/unresolved buckets, adding modest meaning rather than new syntax or constraints, so 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?

The description gives a specific verb+resource ('Gemessene Wohnfläche ... aufteilen') and states the aggregation outcome (eligible, excluded, unresolved sums). An agent can identify this as a status-based area aggregation, though it never names a sibling such as saugwischer_bodenfreigabe to sharpen the boundary.

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 when-to-use or when-not-to-use guidance and no mention of alternatives, despite several nearby siblings (saugwischer_bodenfreigabe, saugwischer_randstreifen_flaeche) that could plausibly be confused with this one. The agent must infer applicability from the purpose statement alone.

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