Skip to main content
Glama

getecoback-climate-weather

hoerprobe_zwei_betriebsarten_subjektive_urteile

Read-only

Verdichtet paarweise persönliche Höreindrücke mit getrenntem Unentschieden — Summarize paired listening preferences while keeping undecided trials visible.

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": {
      "a_angenehmer": "<a_angenehmer>",
      "b_angenehmer": "<b_angenehmer>",
      "unentschieden": "<unentschieden>",
      "gleicher_hoerplatz": "<gleicher_hoerplatz>"
    },
    "name": "hoerprobe_zwei_betriebsarten_subjektive_urteile"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_angenehmerYesAnzahl eigener Vergleichsdurchgänge mit Präferenz für A.
b_angenehmerYesAnzahl mit Präferenz für B.
unentschiedenYesVergleiche ohne eindeutige Präferenz.
gleicher_hoerplatzYesWar der Hörplatz bei allen Durchgängen gleich?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 covered. The description adds one genuine behavioral fact beyond that — undecided trials stay visible in the result instead of being dropped — but says nothing about the shape of the summary (counts, ratios, verdict) for a tool with 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?

Two short sentences with zero filler, front-loading the core action before the undecided-qualms caveat. The German and English renderings are near-duplicates, which is mildly redundant but keeps the definition scannable for either language.

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?

This is a simple aggregation tool with four fully documented required parameters, so the burden is modest. However, with no output schema, the description should indicate what the condensed summary contains (counts per side, undecided tally, effect/verdict) and it does not.

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%, with all four parameters individually documented (a_angenehmer, b_angenehmer, unentschieden, gleicher_hoerplatz). The description only echoes 'paarweise' and 'Unentschieden' and adds no interpretation, units, or constraints beyond the schema, so 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 names a specific verb+resource pair ('Verdichtet'/'Summarize' paired listening preferences) and adds a distinguishing scope detail: undecided trials are kept separate rather than folded in. That is clear enough to tell it apart from the synchronization and measurement siblings, though it never names an alternative explicitly.

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 or when-not-to-use guidance, no prerequisite statement (e.g., that counts must come from the same listening position), and no routing to a sibling. The agent must infer from the phrasing that this is an aggregation step for pairwise preference counts.

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