Skip to main content
Glama

getecoback-raumklima

vergleichstest_gewichtung_rangwechsel

Read-only

Prüfe, ob andere Prioritäten die Reihenfolge zweier belegter Testprofile drehen — Check whether a user weighting reverses two documented test profiles

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_aufgabe": "<a_aufgabe>",
      "a_pflege": "<a_pflege>",
      "b_aufgabe": "<b_aufgabe>",
      "b_pflege": "<b_pflege>",
      "gewicht_bericht": "<gewicht_bericht>",
      "gewicht_eigen": "<gewicht_eigen>",
      "vergleichbare_teilnoten": "<vergleichbare_teilnoten>"
    },
    "name": "vergleichstest_gewichtung_rangwechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_pflegeYesTestpunkte A für Pflege auf derselben Skala
b_pflegeYesTestpunkte B für denselben Pflegeaspekt
a_aufgabeYesTestpunkte A für Aufgabe auf einer gemeinsamen Skala von 0 bis 100
b_aufgabeYesTestpunkte B für dieselbe Aufgabe
gewicht_eigenYesEigener Aufgabenanteil für einen Vergleich in Prozent
gewicht_berichtYesAnteil der Aufgabe in der nachgewiesenen Testgewichtung in Prozent
vergleichbare_teilnotenYesBeide Teilnoten stammen aus demselben Test oder nachweislich gleichem Verfahren, mehr Punkte ist jeweils besser

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 the prerequisite that profiles be 'belegt' (documented) and comparable, but it never says what the check produces — a boolean verdict, a swapped ordering, or a margin — which matters because no output schema exists.

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 definition is a single front-loaded clause with no filler. The German phrase and its English rendering are largely duplicative, which costs a little density but does aid clarity for mixed-language agents.

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 seven-required-parameter computation with no output schema and no annotation detail beyond read-only/local, the description should state the nature of the result. It conveys the question being asked but leaves the answer format and the meaning of a positive versus negative outcome unspecified.

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 all seven parameters are documented in the schema itself, including the scale and unit hints. The description adds nothing about the two weighting parameters or how the 'vergleichbare_teilnoten' precondition interacts with the computation, so the baseline of 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 ('Prüfe') and a specific object (whether a different weighting reverses the rank order of two documented test profiles), which is more precise than the bare tool name. It does not, however, explicitly distinguish itself from near-name siblings such as vergleichstest_gleiche_prueflinge_querwert or vergleichstest_teilnoten_spannweite_luecke.

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

Usage Guidelines3/5

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

Usage is only implied: the agent can infer the tool applies when two documented profiles are compared under an alternative weighting scheme. There is no explicit statement of when not to use it and no named alternative tool for related comparison tasks.

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