Skip to main content
Glama
zafronix

World Cup History MCP

list_matches

Filter FIFA World Cup matches by year, stage, or date. Returns kickoff time, teams, score, stadium, and attendance for each match.

Instructions

List World Cup matches. Filterable by year and/or stage (group_a..group_h, round_of_16, quarter_final, semi_final, third_place, final). Returns kickoff time, home/away team, score, stadium, attendance. Use this for "show me all the 1990 group matches" or "list every World Cup final". Pair with get_match for a specific match's full details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNo
stageNo
dateNo

Implementation Reference

  • The handler function for the 'list_matches' tool. Constructs query params from optional year/stage/date arguments and calls the API endpoint /matches with them.
    handler: async (args: { year?: number; stage?: string; date?: string }) => {
      const params = new URLSearchParams();
      if (args.year)  params.set('year',  String(args.year));
      if (args.stage) params.set('stage', args.stage);
      if (args.date)  params.set('date',  args.date);
      const q = params.toString();
      return api(`/matches${q ? `?${q}` : ''}`);
    },
  • Zod schema for 'list_matches' tool input validation. Accepts optional year (int 1930-2030), stage (string), and date (YYYY-MM-DD string).
    schema: z.object({
      year:  z.number().int().min(1930).max(2030).optional().describe('Tournament year (optional)'),
      stage: z.string().optional().describe('Stage filter, e.g. "final", "semi_final", "group_a"'),
      date:  z.string().optional().describe('YYYY-MM-DD — match-day filter (optional)'),
    }).strict(),
  • src/index.ts:252-271 (registration)
    Tool registration entry in the tools array. Defines name ('list_matches'), description explaining usage, binds schema and handler together.
    name: 'list_matches',
    description:
      'List World Cup matches. Filterable by year and/or stage (group_a..group_h, ' +
      'round_of_16, quarter_final, semi_final, third_place, final). Returns kickoff time, ' +
      'home/away team, score, stadium, attendance. Use this for "show me all the 1990 ' +
      'group matches" or "list every World Cup final". Pair with get_match for a specific ' +
      'match\'s full details.',
    schema: z.object({
      year:  z.number().int().min(1930).max(2030).optional().describe('Tournament year (optional)'),
      stage: z.string().optional().describe('Stage filter, e.g. "final", "semi_final", "group_a"'),
      date:  z.string().optional().describe('YYYY-MM-DD — match-day filter (optional)'),
    }).strict(),
    handler: async (args: { year?: number; stage?: string; date?: string }) => {
      const params = new URLSearchParams();
      if (args.year)  params.set('year',  String(args.year));
      if (args.stage) params.set('stage', args.stage);
      if (args.date)  params.set('date',  args.date);
      const q = params.toString();
      return api(`/matches${q ? `?${q}` : ''}`);
    },
Behavior4/5

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

Despite no annotations, it describes the return fields (kickoff time, teams, etc.) and indicates read-only behavior. Lacks details on pagination or limits.

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?

Two sentences that front-load the purpose and provide examples, with no wasted words.

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?

Adequately explains return fields and usage context for a list tool, and references sibling tool for deeper details.

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 has 0% coverage; description explains 'year' and 'stage' filters with examples but does not mention the 'date' parameter.

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 clearly states it lists World Cup matches, specifies filterable fields (year, stage) with examples, and distinguishes from the sibling get_match tool.

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?

Provides explicit query patterns ('show me all the 1990 group matches') and mentions pairing with get_match for details, but does not explicitly state when not to use it.

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