Skip to main content
Glama
zafronix

World Cup History MCP

list_tournaments

Retrieve a complete list of all FIFA World Cup tournaments from 1930 to 2026, including host countries and champions.

Instructions

List every FIFA World Cup tournament (1930 → 2026) with year, host country list, champion (or null for the upcoming 2026 cup). Useful as a starting point when the user is exploring history or needs to disambiguate a year.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:113-122 (registration)
    The 'list_tournaments' tool is defined as part of the 'tools' array. It has a name, description, empty zod schema (no arguments), and a handler that calls the api('/tournaments') endpoint. This is both the registration and the handler definition since everything is in one file.
    const tools = [
      {
        name: 'list_tournaments',
        description:
          'List every FIFA World Cup tournament (1930 → 2026) with year, host country list, ' +
          'champion (or null for the upcoming 2026 cup). Useful as a starting point when the ' +
          'user is exploring history or needs to disambiguate a year.',
        schema: z.object({}).strict(),
        handler: async () => api('/tournaments'),
      },
  • The handler for 'list_tournaments' is an async arrow function that calls api('/tournaments'), which makes a GET request to the base API path /fifa/worldcup/v1/tournaments.
    handler: async () => api('/tournaments'),
  • The input schema for 'list_tournaments' is an empty strict zod object (z.object({}).strict()), meaning no arguments are accepted.
    schema: z.object({}).strict(),
Behavior3/5

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

No annotations are provided, so the description carries the burden. It correctly indicates a read operation (listing). However, it does not disclose any potential pagination, sorting, or ordering behavior, even though the schema has no parameters. The description is adequate but lacks depth on behavioral traits beyond the listing itself.

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?

The description is two sentences long, clearly front-loaded with the main action, and every word adds value. There is no redundancy or filler.

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

Completeness5/5

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

For a tool with no parameters and no output schema, the description fully explains what the tool does, the data range, and the specific fields returned. It is complete and leaves no ambiguity for an agent.

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?

The input schema has no parameters, so schema coverage is 100%. The description adds meaning by explaining the fields returned (year, host countries, champion) and the special case of null for 2026. This provides clarity beyond the empty schema, earning a baseline plus increment.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the tool lists all FIFA World Cup tournaments with specific fields (year, host, champion) across a defined range (1930-2026). This is a specific verb+resource combination that clearly distinguishes from siblings like 'get_tournament' which returns details of one tournament.

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?

The description notes it is useful as a starting point for exploring history or disambiguating a year, which implies contexts for use. However, it does not explicitly mention when not to use it or name alternative tools, though siblings like 'get_tournament' or 'compare_tournaments' are implied alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zafronix/wc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server