Skip to main content
Glama

getecoback-climate-weather

klimalog_zeitpaar_naechster_eindeutiger_wert

Read-only

Einen Verbrauchspunkt dem eindeutig nächstliegenden von zwei Klimawerten zuordnen — Pair an anchor sample to its unique nearest timestamp within a chosen tolerance.

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": {
      "anker_s": "<anker_s>",
      "vorher_s": "<vorher_s>",
      "nachher_s": "<nachher_s>",
      "toleranz_s": "<toleranz_s>"
    },
    "name": "klimalog_zeitpaar_naechster_eindeutiger_wert"
  }
}

Input Schema

NameRequiredDescriptionDefault
anker_sYesZeit des Verbrauchspunkts ab gemeinsamer Referenz in Sekunden.
vorher_sYesZeit des unmittelbar vorhergehenden Klimawerts in Sekunden, exakt gleichzeitig möglich.
nachher_sYesZeit des unmittelbar nachfolgenden Klimawerts in Sekunden, exakt gleichzeitig möglich.
toleranz_sYesMaximal vertretbarer Zeitabstand für die Messaufgabe.

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 a read-only, closed-world operation, so the safety profile is covered. The description adds the meaningful behavioral constraint that the match must be unique, hinting at an ambiguity case, but it never says how ties or out-of-tolerance cases are reported and never describes the result. With annotations present, this is adequate but thin.

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?

A single front-loaded sentence with the core pairing rule first and the tolerance qualifier second, repeated bilingually. No filler sentences, though the duplicated German/English phrasing is slightly redundant for an agent.

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 4-parameter, read-only matching primitive with no output schema, the definition should still say what comes back (matched timestamp, which side, or a failure) and how ambiguity resolves. Those gaps remain, leaving the agent to guess the return contract even though the input contract is fully covered by the schema.

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 in the schema. The description only glosses 'toleranz_s' as a chosen tolerance and 'anker_s' as a consumption point, adding no format, unit, or boundary semantics beyond what the schema states. 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 states a concrete verb and resource: it pairs an anchor (consumption) sample to the uniquely nearest of two climate timestamps, within a tolerance. The 'eindeutig' qualifier signals the distinguishing constraint. It does not explicitly contrast itself with any sibling, but the operation is specific enough to be recognizable.

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?

Use is implied by the wording ('within a chosen tolerance', 'unique nearest'), so an agent can infer you call it when you need an unambiguous neighbor assignment. However, there is no explicit when-to-use vs. when-not statement, no mention of what to do if neither neighbor falls inside the tolerance, and no named alternative.

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