Skip to main content
Glama

Prorakel · Fußball-Prognosen

Aktueller Spieltag

spieltag
Read-onlyIdempotent

Alle Partien des aktuellen Spieltags eines Wettbewerbs mit der Tendenz von Prorakel (Heimsieg, Unentschieden oder Auswärtssieg); nach dem Abpfiff mit Endstand und ob die Tendenz getroffen hat. Verfügbar für Bundesliga, 2. Bundesliga, 3. Liga, Premier League, La Liga, Serie A, Ligue 1, Eredivisie, Österreich, Schweiz, Champions League und Europa League.

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": "spieltag"
  }
}

Input Schema

NameRequiredDescriptionDefault
wettbewerbYesCode des Wettbewerbs, z. B. BL1 für die Bundesliga.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / wettbewerb / enum
      Previous value: -[
      -  "BL1",
      -  "BL2",
      -  "BL3",
      -  "EN1",
      -  "ES1",
      -  "IT1",
      -  "FR1",
      -  "NL1",
      -  "AT1",
      -  "CH1",
      -  "CL",
      -  "EL"
      -]New value: +[
      +  "BL1",
      +  "BL2",
      +  "BL3",
      +  "EN1",
      +  "ES1",
      +  "IT1",
      +  "FR1",
      +  "TR1",
      +  "NL1",
      +  "AT1",
      +  "CH1",
      +  "CL",
      +  "EL"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no repeating. The description adds genuine behavioral context the annotations lack: the response shape changes over time – tendency before the final whistle, final score plus a hit/miss indicator for the tendency afterwards. Auth and rate-limit behavior remain unstated.

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 sentences, front-loaded with the resource and result semantics before the availability list. The second sentence is a long enumeration but every element maps to an allowed enum value, so it earns its space. A semicolon rather than a full stop makes the first sentence slightly dense.

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?

There is no output schema, and the description compensates by explaining exactly what is returned and how it differs pre- and post-match. The only real gap is the incomplete league enumeration against the enum, which leaves a small hole an agent could trip on.

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 enum parameter is already documented, so the baseline of 3 applies. The description does add value by expanding the cryptic codes into league names, but its list omits TR1, which the enum accepts, so an agent could wrongly conclude the Turkish league is unsupported.

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 states a concrete resource and scope: all matches of the current matchday for one competition, enriched with Prorakel's tendency and final result. That is far beyond the bare name 'spieltag'. It does not, however, differentiate itself from the sibling spiele_am_tag, which an agent might plausibly confuse with it.

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 through 'aktueller Spieltag' – the agent can infer this is the tool for the current round rather than an arbitrary date. There is no statement about when not to use it, and no pointer to spiele_am_tag for other dates or to wettbewerbe for competition metadata.

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