Skip to main content
Glama

getecoback-raumklima

messprotokoll_zeitpaarung_viele_zeilen

Read-only

Vor dem Zusammenführen von Klima- und Verbrauchsprotokoll künstlich vervielfachte Zeilen im Zeitjoin erkennen — Quantify many-to-many row inflation before joining timestamped logs.

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": {
      "andere_eindeutige_paare": "<andere_eindeutige_paare>",
      "klima_zeilen_zeit": "<klima_zeilen_zeit>",
      "verbrauch_zeilen_zeit": "<verbrauch_zeilen_zeit>"
    },
    "name": "messprotokoll_zeitpaarung_viele_zeilen"
  }
}

Input Schema

NameRequiredDescriptionDefault
klima_zeilen_zeitYesKlimazeilen am fraglichen gemeinsamen Zeitstempel.
verbrauch_zeilen_zeitYesVerbrauchszeilen an demselben Zeitstempel.
andere_eindeutige_paareYesEins-zu-eins-Paare außerhalb des fraglichen Zeitstempels.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare a safe read-only, closed-world operation. The description adds that this is a pre-join diagnostic for row inflation, but it does not explain the result format or calculation behavior beyond that.

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 description is compact and front-loads the trigger condition before the tool's purpose. The German and English clauses restate the same idea, which is slightly redundant but still efficient.

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 three-parameter diagnostic with no output schema, the description explains the input context but not what the quantified result looks like or how to interpret it. It is adequate for invoking the tool but incomplete for understanding its return.

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%, and the schema already defines each count parameter clearly. The description adds no additional meaning about parameter interpretation or constraints beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific action (erkennen/quantify), a precise resource (many-to-many row inflation in a time join), and the domain (climate and consumption logs). An agent can distinguish this diagnostic from generic joining or logging tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use this before merging timestamped logs, giving a clear trigger context. It does not name alternatives or state when not to use it, so it falls short of full routing guidance.

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