Skip to main content
Glama

Read a league round’s fixtures

get_league_fixtures
Read-onlyIdempotent

Lists the pairings, fixture keys and results in one round of a group’s league. The first open round is the default. Only organizers can read a draft draw. Requires mcp:read.

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": {
      "token": "<token>"
    },
    "name": "get_league_fixtures"
  }
}

Input Schema

NameRequiredDescriptionDefault
roundNo
tokenYes
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description still adds real value beyond that: round defaulting to the first open round, the organizer-only restriction on draft draws, and the mcp:read scope requirement. It stops short of stating what a caller sees for an unpublished/empty round or how results appear for unplayed fixtures.

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?

Three short sentences, front-loaded with what is returned before the defaulting rule and permission caveat. Every sentence carries information; a slightly tighter grouping of the default-round and organizer constraints would make it ideal.

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?

No output schema exists, and the description does cover the return contents (pairings, fixture keys, results), which is the key gap for a read tool. With four parameters, one undocumented beyond the schema, and strong annotations, the remaining omission is edge-case behavior for drafts or empty rounds.

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 50%; the two analytics parameters (llm_model, conversation_id) are self-documented, while round and token are not. The description partially compensates by explaining that omitting round selects the first open round, which is genuinely useful semantics the schema lacks (round has no default). It says nothing about token's meaning or format beyond the mcp:read scope hint.

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?

Names a specific verb and resource with scope: "Lists the pairings, fixture keys and results in one round of a group's league." The read-only framing implicitly separates it from sibling write tools like draw_league and report_league_result, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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

Usage Guidelines4/5

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

Gives concrete context for when the call is valid: the first open round is used by default, and only organizers may read a draft draw. That tells an agent both the default path and a permission boundary. No alternatives or when-not-to-use routing (e.g., versus draw_league before a draw exists) are offered.

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