Skip to main content
Glama

getecoback-climate-weather

raumgrundriss_l_flaeche

Read-only

Grundfläche eines L-förmigen Raums aus Außenmaß und rechteckiger Aussparung ermitteln — Measure an L-shaped room footprint from an enclosing rectangle and one corner cutout.

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": {
      "aussen_breite_m": "<aussen_breite_m>",
      "aussen_tiefe_m": "<aussen_tiefe_m>",
      "ausschnitt_breite_m": "<ausschnitt_breite_m>",
      "ausschnitt_tiefe_m": "<ausschnitt_tiefe_m>"
    },
    "name": "raumgrundriss_l_flaeche"
  }
}

Input Schema

NameRequiredDescriptionDefault
aussen_tiefe_mYesTiefe des umschließenden Rechtecks, innen gemessen.
aussen_breite_mYesBreite des umschließenden Rechtecks, innen gemessen.
ausschnitt_tiefe_mYesTiefe der Eck-Aussparung.
ausschnitt_breite_mYesBreite der rechteckigen Eck-Aussparung.

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 the safety profile is covered. The description adds the computational model (enclosing area minus a corner cutout), which is genuinely useful, but it stays silent on output unit/format and on edge cases such as a cutout exceeding the enclosing rectangle.

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 compact clauses, one per language, with the resource and the geometric model front-loaded and no filler. The German/English duplication adds length but is a deliberate bilingual convention rather than padding.

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 computation tool with no output schema, the definition never states what comes back — a bare number, a unit (m²), or a rounded value. Inputs are complete via the schema and the geometry is clear, so the remaining gap is the return contract.

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%, so the four dimension parameters are already fully documented, giving a baseline of 3. The description confirms the outer dimensions form a single enclosing rectangle and that only one cutout is expected, a minor addition over the 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?

Names a specific verb and resource: "Grundfläche eines L-förmigen Raums ... ermitteln", and pins the geometry down as an enclosing rectangle with a rectangular corner cutout. An agent can tell it apart from area-style siblings such as saugwischer_randstreifen_flaeche by the L-shape input model, but the description never names an alternative or a boundary explicitly.

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?

Applicability is only implied: the tool handles exactly one L-shape with a single corner cutout, which implicitly scopes out other footprint shapes. There is no explicit when-to-use statement, no prerequisite, and no routing to any sibling tool.

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