Skip to main content
Glama

getecoback-climate-weather

messreihe_echte_wiederholungen_zaehlen

Read-only

Messpunkte von unabhängig neu begonnenen Versuchsläufen trennen — Count independent household trials without treating every logger sample as a replicate.

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": {
      "punkte": "<punkte>",
      "abgeschlossene_laeufe": "<abgeschlossene_laeufe>",
      "separat_neu_gestartet": "<separat_neu_gestartet>"
    },
    "name": "messreihe_echte_wiederholungen_zaehlen"
  }
}

Input Schema

NameRequiredDescriptionDefault
punkteYesZahl der Einzelwerte innerhalb aller Läufe.
abgeschlossene_laeufeYesZahl vollständiger Durchgänge mit Messpunkten.
separat_neu_gestartetYesDavon neu unter eigenen Ausgangsbedingungen begonnene Durchgänge.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already establish that this is a safe, closed-world, read-only calculation, so the description need not restate safety. It adds one real behavioral point: raw logger samples are not replicates, only separately restarted runs count. It says nothing about how the count is derived, whether inputs are validated against each other, or what the returned value is.

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?

One compact bilingual sentence with the corrective purpose front-loaded and no filler. The German/English duplication costs a little space but serves precision in a domain with mixed terminology.

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, fully documented calculation tool with read-only annotations and no output schema, the description is adequate at the conceptual level. It leaves out the actual formula and the shape of the result, which an agent needs to interpret the returned number correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description goes slightly beyond by framing the meaning behind the inputs, namely measurement points versus independently restarted trials. It still does not say how separat_neu_gestartet relates arithmetically to abgeschlossene_laeufe or which of the three parameters drives the result.

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 concrete operation on a concrete resource: separate measurement points belonging to independently restarted runs, and count independent household trials rather than every logger sample. That is more specific than a restatement of the German name, though the actual computation is left implicit, so an agent knows the intent but not exactly the arithmetic.

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 statement of when to call this versus the sibling that plans replicates (stromversuch_wiederholungen_planen) or the outlier tool. The 'without treating every logger sample as a replicate' clause hints at the counting decision but gives no preconditions, exclusions, or alternative routing.

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