Skip to main content
Glama

getecoback-climate-weather

dachraum_hitzetrend_erstes_ziel_nach_trendknick

Read-only

Erkenne, ob eine Zieltemperatur erstmals vor oder nach dem beobachteten Trendknick lag — Identify in which observed trend segment the temperature target first appeared

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": {
      "start_c": "<start_c>",
      "knick_c": "<knick_c>",
      "ende_c": "<ende_c>",
      "ziel_c": "<ziel_c>",
      "gleiche_stelle": "<gleiche_stelle>"
    },
    "name": "dachraum_hitzetrend_erstes_ziel_nach_trendknick"
  }
}

Input Schema

NameRequiredDescriptionDefault
ende_cYesWert der späteren Ablesung
ziel_cYesEigener oberer Zielwert
knick_cYesWert an dem zuvor dokumentierten Wechselpunkt
start_cYesErster Wert am vereinbarten Messort
gleiche_stelleYesAlle Werte stammen vom gleichen repräsentativen Raumpunkt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/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. Beyond that the description adds no behavioural context: it does not say what the result looks like (a segment label? a boolean?), what happens when the target is never reached, or how a failed 'gleiche_stelle' condition is handled.

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?

The sentence is front-loaded and contains no filler within each language, but the German and English versions say exactly the same thing, doubling the length without adding information. The core statement nevertheless appears first, which keeps it usable.

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 five-parameter, fully required tool with no output schema, the definition is only minimally complete: it explains the question being answered but not the answer's form or edge cases (target never crossed, values not from the same point). The schema carries the input semantics, so the gaps are moderate rather than fatal.

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 every parameter is already documented in the schema and the baseline is 3. The description mentions the target temperature and the trend break, mapping loosely onto ziel_c and knick_c, but contributes no extra meaning such as ordering constraints or how the first appearance is determined between the three readings.

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 names a specific analytical operation (determining whether a target temperature first occurred before or after the observed trend break) rather than restating the tool name, so an agent can tell this is a trend-segmentation/classification tool. It does not, however, distinguish itself from near-neighbours such as 'vergleichstest_ziel_vorab_oder_nachtraeglich', which appear to address a similar before/after-target question.

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 statement of prerequisites, even though the tool requires all five values to come from the same measurement point (gleiche_stelle). The agent must infer applicability from the description alone, and nothing points to an alternative tool for the same question.

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