Skip to main content
Glama

getecoback-raumklima

testfelder_gemeinsame_modelle_abgrenzen

Read-only

Überlappung zweier Testfelder aus exakten Modellvarianten bestimmen — Measure exact-model overlap before comparing two test cohorts.

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": {
      "modellzahl_a": "<modellzahl_a>",
      "modellzahl_b": "<modellzahl_b>",
      "exakt_gemeinsam": "<exakt_gemeinsam>",
      "abgleich_abgeschlossen": "<abgleich_abgeschlossen>"
    },
    "name": "testfelder_gemeinsame_modelle_abgrenzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellzahl_aYesAnzahl geprüfter Varianten in Testfeld A.
modellzahl_bYesAnzahl geprüfter Varianten in Testfeld B.
exakt_gemeinsamYesAnzahl in beiden Feldern exakt identifizierter Varianten.
abgleich_abgeschlossenYesSind alle Variantenkennungen überprüft?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 usefully adds that matching is on EXACT model variants rather than approximate identity, but for a computation tool with no output schema it never says what is produced (overlap count, ratio, or verdict) nor how the required flag 'abgleich_abgeschlossen' affects the result.

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 compact clauses with the operation front-loaded and no filler; nothing is buried. The German/English duplication is slightly redundant for a single reader but serves a bilingual audience and costs little space.

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 read-only calculation with a fully documented 4-parameter schema, the main missing element is the nature of the result, since no output schema exists to explain the return value. The description is otherwise sufficient to call the tool correctly, but leaves the agent guessing about the outcome format.

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% and each of the four parameters carries its own German description (counts in field A and B, exact matches, and whether all identifiers were checked), so the schema does the heavy lifting. The description's 'aus exakten Modellvarianten' reinforces the semantics of exakt_gemeinsam but adds little that the schema does not already state.

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 (bestimmen/measure) on a specific object (the overlap of two test fields, based on exact model variants), so an agent knows precisely what is computed. It does not explicitly differentiate itself from any sibling tool, which keeps it below a 5.

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?

The clause 'before comparing two test cohorts' implies the temporal context in which this tool applies, which is useful. However, there is no statement of when not to use it, no prerequisites (e.g. that the reconciliation must already be finished), and no named alternative for non-exact or fuzzy comparisons.

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