Skip to main content
Glama

getecoback-climate-weather

ab_haushaltsversuch_stoerfaktoren

Read-only

Vor einer A/B-Messung fehlende Kontrollen für einen fairen Vergleich markieren — Review workload, endpoints and changed settings before testing.

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": {
      "gleiche_aufgabe": "<gleiche_aufgabe>",
      "gleiches_ergebnis": "<gleiches_ergebnis>",
      "nur_eine_aenderung": "<nur_eine_aenderung>",
      "kontext_protokolliert": "<kontext_protokolliert>"
    },
    "name": "ab_haushaltsversuch_stoerfaktoren"
  }
}

Input Schema

NameRequiredDescriptionDefault
gleiche_aufgabeYesIst dieselbe Haushaltsaufgabe mit derselben Menge festgelegt?
gleiches_ergebnisYesIst ein gemeinsames, prüfbares Ende festgelegt, etwa gleicher Trocknungsgrad?
nur_eine_aenderungYesÄndert sich absichtlich nur der untersuchte Faktor?
kontext_protokolliertYesWerden zeitgleich etwa Wetter, Zubehör oder Belegung notiert, soweit für den Versuch relevant?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds that this is a pre-measurement gate for fair comparisons, but it never says what the tool actually produces when a control is missing (a verdict, a list of flags, a message) — relevant since there is no 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?

One compact sentence with the timing condition front-loaded and no filler. The bilingual duplication of the same idea in German and English is the only redundancy, and it arguably aids comprehension for a non-German reader.

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 four-boolean read-only predicate tool with no output schema, the description covers the 'when' but not the 'what comes back' — whether results are per-criterion flags, an aggregate pass/fail, or textual guidance. An agent can call it correctly, but cannot anticipate the response shape.

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 the four booleans are already fully self-documenting; baseline 3 applies. The English gloss ('workload, endpoints and changed settings') loosely echoes three of the four parameters and omits kontext_protokolliert, adding no meaning beyond the schema.

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 action ('fehlende Kontrollen markieren') and a specific context ('Vor einer A/B-Messung'), so the agent knows this is a pre-test fairness/confounder check rather than a measurement or data-fetch tool. It does not explicitly contrast itself with any sibling, and the mixed German/English phrasing slightly blurs the single stated purpose.

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?

'Vor einer A/B-Messung' / 'before testing' clearly states the point in the workflow where this should be invoked, which is genuine when-to-use guidance. There is no statement of when-not to use it and no named alternative for related checks, so it stops 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