Skip to main content
Glama

getecoback-climate-weather

raumfeuchte_abschnitte_zeitgewichtet

Read-only

Mittelwerte zweier unterschiedlich langer Messabschnitte zeitgewichtet zusammenfassen — Combine comparable humidity period averages without giving a short period the same weight as a long one.

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": {
      "a_mittel_rh": "<a_mittel_rh>",
      "a_min": "<a_min>",
      "b_mittel_rh": "<b_mittel_rh>",
      "b_min": "<b_min>"
    },
    "name": "raumfeuchte_abschnitte_zeitgewichtet"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_minYesDauer von Abschnitt A, in Minuten.
b_minYesDauer von Abschnitt B, in Minuten.
a_mittel_rhYesZeitmittel von Abschnitt A, in %. Kein Einzelwert.
b_mittel_rhYesZeitmittel von Abschnitt B, in %. Kein Einzelwert.

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 this as a read-only, closed-world operation, and the description adds the important behavioral detail that the combination is time-weighted rather than a simple mean. It does not disclose the exact formula, output form, rounding behavior, or edge-case handling, which limits transparency for a calculation tool without an output schema.

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 definition is short and front-loads the core operation before explaining the weighting rationale. The bilingual structure repeats the same idea, which is mildly redundant but not harmful.

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 complete schema documentation and read-only annotations, most needed context is present. However, since there is no output schema, the description could make the return value more explicit, such as stating that it returns a single time-weighted humidity mean in percent.

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?

The input schema has 100% description coverage and fully documents the four parameters, including units and meaning. The description does not add parameter-level detail beyond the schema, so the baseline score of 3 is 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 operation: time-weighted aggregation of two humidity period averages of different lengths. It clearly identifies the resource and the key distinction from a naive average, but does not explicitly distinguish itself from similarly named sibling tools.

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 phrase 'without giving a short period the same weight as a long one' implies the tool should be used when combining averages from unequal-duration periods. However, it gives no explicit when-not guidance, prerequisites, or named alternative, so the usage context remains implicit.

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