Skip to main content
Glama

getecoback-raumklima

luftoeffnung_teilflaechen_nettostrom

Read-only

Schätzt den Nettostrom durch zwei Teilflächen mit beobachteter Gegenströmung — Estimate net flow through two opening sections carrying opposing flow.

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": {
      "hinein_flaeche_m2": "<hinein_flaeche_m2>",
      "hinein_m_s": "<hinein_m_s>",
      "heraus_flaeche_m2": "<heraus_flaeche_m2>",
      "heraus_m_s": "<heraus_m_s>"
    },
    "name": "luftoeffnung_teilflaechen_nettostrom"
  }
}

Input Schema

NameRequiredDescriptionDefault
heraus_m_sYesMittlere Geschwindigkeit senkrecht auswärts über diese Teilfläche in m/s.
hinein_m_sYesMittlere Geschwindigkeit senkrecht einwärts über diese Teilfläche in m/s.
heraus_flaeche_m2YesFreie, auswärts durchströmte Teilfläche in m².
hinein_flaeche_m2YesFreie, einwärts durchströmte Teilfläche in m².

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the result is an estimate and that the flow is opposing, but it does not explain the return value, sign convention, or calculation assumptions.

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

Conciseness5/5

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

The description is two short bilingual sentences with no wasted wording. The core purpose is front-loaded and immediately understandable.

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 calculation tool with no output schema, the description explains the physical scenario but omits the return value and sign convention, which are important for interpreting net flow with opposing directions. It is adequate but leaves a meaningful 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%, so all four parameters are already documented with units and meanings. The description reinforces the two-section opposing-flow setup but adds no parameter-level detail beyond what the schema provides, making the baseline 3 appropriate.

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 states a specific verb ('Schätzt' / 'Estimate') and a specific resource ('Nettostrom' / 'net flow') through two opening sections with opposing flow. It is clear what the tool computes, but it does not explicitly distinguish itself from any sibling tool.

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?

The scenario 'two opening sections carrying opposing flow' implies when the tool is applicable, but there is no explicit when-to-use guidance, no exclusions, and no named alternative. The agent must infer the usage context from the physical setup described.

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