Skip to main content
Glama

getecoback-raumklima

vergleichstest_ziel_vorab_oder_nachtraeglich

Read-only

Unterscheide vorab definierte Vergleichskriterien von nachträglich ausgewählten Beobachtungen — Distinguish preregistered criteria from retrospectively selected observations

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": {
      "kriterium_vor_lauf": "<kriterium_vor_lauf>",
      "grenze_vor_lauf": "<grenze_vor_lauf>",
      "identische_auswertung": "<identische_auswertung>"
    },
    "name": "vergleichstest_ziel_vorab_oder_nachtraeglich"
  }
}

Input Schema

NameRequiredDescriptionDefault
grenze_vor_laufYesGrenzwert und Richtung des Kriteriums wurden dort vorab festgehalten
kriterium_vor_laufYesKriterium steht in der vor Beginn datierten Methodik
identische_auswertungYesStichprobe und Auswertung entsprechen der damaligen Festlegung

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 the safety profile is known and the bar is lower. The description adds the conceptual distinction the tool adjudicates, but not how the three status values combine into a judgment, what happens when values conflict (e.g. criterion 'belegt' but evaluation 'ausgeschlossen'), or what the response contains. Some value beyond annotations, but thin for a judgment tool.

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 no filler. The German/English duplication is mildly redundant, but the bilingual restatement is short and does aid disambiguation of the technical terms rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carries the burden of explaining the return value — and it does not. For a three-required-enum judgment tool whose whole point is producing a 'vorab vs. nachträglich' determination, an agent cannot tell what it will receive back or how to interpret a mixed result.

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 all three parameters carry their own German descriptions plus a shared belegt/ausgeschlossen/offen enum, so the schema does the work. The description does not add per-parameter meaning — it does not explain that all three must be satisfied for a 'preregistered' verdict, nor what 'offen' implies for the outcome.

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 operation (distinguish/classify) and the two things being separated: preregistered comparison criteria versus retrospectively selected observations. It is not a tautology of the name, but it never says what the tool actually emits — a verdict, a per-criterion classification, or a checklist — and it does not distinguish itself from the other 'vergleichstest_*' siblings.

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 statement, no prerequisite, and no exclusion. Given siblings such as vergleichstest_gewichtung_rangwechsel, vergleichstest_teilnoten_spannweite_luecke, and vergleichstest_typischer_wert_quantilangabe, the agent gets no signal about which comparison-test tool applies to a preregistration question versus a weighting or quantile 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