Skip to main content
Glama

Whistle.day - Tournament organizer

list_fixtures

Read-onlyIdempotent

List fixtures in a stage, optionally filtered by pool, round, or status

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": {
      "stage_id": "<stage_id>"
    },
    "name": "list_fixtures"
  }
}

Input Schema

NameRequiredDescriptionDefault
roundNoRound number (optional)
statusNoStatus filter: pending, ready, live, finished, walkover, bye (optional)
pool_idNoPool ID (optional)
stage_idYesStage ID

Output Schema

NameRequiredDescriptionDefault
fixturesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "fixtures": {
      +      "items": {
      +        "properties": {
      +          "away_entry": {
      +            "description": "Entry ID of the away side, empty until it is known",
      +            "type": "string"
      +          },
      +          "away_score": {
      +            "description": "Away score: sets, or goals",
      +            "type": "integer"
      +          },
      +          "code": {
      +            "description": "Short handle for the match, e.g. A1 or QF2",
      +            "type": "string"
      +          },
      +          "court": {
      +            "description": "Court ID, empty when unassigned",
      +            "type": "string"
      +          },
      +          "home_entry": {
      +            "description": "Entry ID of the home side, empty until it is known",
      +            "type": "string"
      +          },
      +          "home_score": {
      +            "description": "Home score: sets, or goals",
      +            "type": "integer"
      +          },
      +          "id": {
      +            "description": "Record ID",
      +            "type": "string"
      +          },
      +          "pool": {
      +            "description": "Pool ID, empty when the stage has no pools",
      +            "type": "string"
      +          },
      +          "position": {
      +            "description": "Order, 0-based; in a table, the rank",
      +            "type": "integer"
      +          },
      +          "round": {
      +            "description": "Round, 0-based",
      +            "type": "integer"
      +          },
      +          "stage": {
      +            "description": "Stage ID",
      +            "type": "string"
      +          },
      +          "status": {
      +            "description": "Status",
      +            "type": "string"
      +          },
      +          "winner": {
      +            "description": "Entry ID of the winner, empty until decided",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "code",
      +          "status",
      +          "round",
      +          "position",
      +          "home_entry",
      +          "away_entry",
      +          "home_score",
      +          "away_score",
      +          "winner",
      +          "court",
      +          "stage",
      +          "pool"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "fixtures"
      +  ],
      +  "type": "object"
      +}
  2. Changed2 schema fields changed
    • removedInput schema / properties / session_token
      Removed value: -{
      -  "description": "The session_token returned by create_tournament",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "stage_id",
      -  "session_token"
      -]New value: +[
      +  "stage_id"
      +]
  3. First observed

TDQS

A3.6/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 fully covered. The description adds no behavioral context beyond that — no pagination, ordering, or empty-result behavior — so it neither earns extra credit nor contradicts anything.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that names the resource, its scope, and the optional filters with zero filler. Nothing could be removed without losing information.

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?

With an output schema present, return values need no explanation, and annotations cover the safety profile; the description is adequate for a simple list operation. It leaves minor gaps around ordering and pagination that an agent might want, but nothing essential is missing.

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 four parameters (including the status enum values and round/pool types) are already documented in the schema. The description merely restates the filterable fields without adding format, semantics, or combination rules, matching the baseline for full schema coverage.

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?

States a specific verb (List) and resource (fixtures) with scope ('in a stage'), which clearly separates it from the singular get_fixture and the mutating update_fixture. It does not explicitly name a sibling or contrast behavior, 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?

'Optionally filtered by pool, round, or status' implies the filtering use case, but there is no explicit when-to-use guidance, no statement of when to prefer get_fixture, and no mention of pagination or ordering concerns. Usage is inferable but not stated.

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