Skip to main content
Glama

Prorakel · Fußball-Prognosen

Saison-Hochrechnung

hochrechnung
Read-onlyIdempotent

Chancen jedes Klubs auf Tabellenbereiche am Saisonende (Meisterschaft, Aufstieg, Relegation, Abstieg) für Bundesliga, 2. Bundesliga, 3. Liga, Serie A, Premier League, Süper Lig, La Liga und Ligue 1 — aus 10.000 simulierten Restsaisons, nach jedem Spieltag neu gerechnet.

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": {
      "wettbewerb": "<wettbewerb>"
    },
    "name": "hochrechnung"
  }
}

Input Schema

NameRequiredDescriptionDefault
wettbewerbYesCode der Liga, z. B. BL1 (Bundesliga) oder IT1 (Serie A).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / wettbewerb / description
      Previous value: -"BL1, BL2 oder BL3."New value: +"Code der Liga, z. B. BL1 (Bundesliga) oder IT1 (Serie A)."
    • changedInput schema / properties / wettbewerb / enum
      Previous value: -[
      -  "BL1",
      -  "BL2",
      -  "BL3"
      -]New value: +[
      +  "BL1",
      +  "BL2",
      +  "BL3",
      +  "IT1",
      +  "EN1",
      +  "TR1",
      +  "ES1",
      +  "FR1"
      +]
  2. 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, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description does add real behavioral context beyond that: the numbers come from 10,000 simulated remaining seasons and are recomputed after every matchday, which tells the agent about data provenance and freshness. It does not describe result shape or ordering, but that is a modest gap for a read-only 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?

One dense but well-formed sentence that front-loads the deliverable (per-club chances by table region) before the league list and the simulation method. No filler. The mid-sentence league enumeration is long but serves a purpose by signalling coverage.

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

Completeness4/5

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

For a one-parameter, read-only tool with no output schema, the description conveys enough: what is computed, for which competitions, from what method, and how fresh it is. Only the shape of the returned data (per-club rows, percentage fields) is left implicit, which is a minor shortfall.

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 coverage is 100% and the single wettbewerb parameter carries an enum plus an inline explanation, so the schema does the heavy lifting. The description's enumeration of the eight supported leagues by name loosely corroborates the enum codes, but adds no syntax or edge-case guidance. Baseline 3 is appropriate.

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 output: per-club probabilities of finishing in table regions (title, promotion, relegation, relegation playoff) for eight named leagues. An agent immediately understands this is a season projection tool, not a fixture or results lookup. It does not explicitly contrast itself with siblings such as bilanz or spieltag, so it stops short of 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?

Usage is only implied by the content: you call it when you want end-of-season probabilities for a league. There is no explicit when-to-use statement, no exclusion of alternatives, and no note that the tool only covers the current season's remaining fixtures.

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