Skip to main content
Glama
zafronix

World Cup History MCP

get_trivia

Retrieve curated trivia and historical facts for any FIFA World Cup year, categorized by record-setting moments, oddities, and context.

Instructions

Curated factual nuggets about a tournament — record-setting moments, oddities, historical context. Each entry is a single fact with category. Use this when the user wants "interesting facts about 1958" or "tell me something I don't know about Italia 90". Far less hallucination-prone than free-recall about old tournaments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNo

Implementation Reference

  • Zod schema for get_trivia — accepts an optional year (integer 1930-2030). No required params.
    schema: z.object({
      year: z.number().int().min(1930).max(2030).optional().describe('Tournament year (optional — omit for all)'),
    }).strict(),
  • Handler function for get_trivia. Calls /trivia endpoint, optionally filtered by year query param.
    handler: async (args: { year?: number }) => {
      const path = args.year ? `/trivia?year=${args.year}` : '/trivia';
      return api(path);
    },
  • src/index.ts:289-303 (registration)
    Tool definition entry in the tools array, registering get_trivia with its name, description, schema, and handler.
    {
      name: 'get_trivia',
      description:
        'Curated factual nuggets about a tournament — record-setting moments, oddities, ' +
        'historical context. Each entry is a single fact with category. Use this when the ' +
        'user wants "interesting facts about 1958" or "tell me something I don\'t know about ' +
        'Italia 90". Far less hallucination-prone than free-recall about old tournaments.',
      schema: z.object({
        year: z.number().int().min(1930).max(2030).optional().describe('Tournament year (optional — omit for all)'),
      }).strict(),
      handler: async (args: { year?: number }) => {
        const path = args.year ? `/trivia?year=${args.year}` : '/trivia';
        return api(path);
      },
    },
Behavior4/5

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

With no annotations, the description must disclose behavior. It reveals that each entry is a single fact with category, and emphasizes low hallucination risk. However, it does not specify any limits on year validity or whether results are guaranteed for all tournaments.

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 extremely concise: two main sentences and a usage example. Every sentence adds value—purpose, output format, and usage guidance. No wasted words.

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 simple tool with one parameter and no output schema, the description fully covers what the tool returns (single facts with category), how to use it (year-based queries), and why it is reliable (curated, less hallucination-prone). No additional context is needed.

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 0%, so the description must clarify the parameter. While the examples ('1958', 'Italia 90') strongly imply the 'year' parameter's purpose, the description never explicitly mentions that the year is used as the query input or explains any constraints (e.g., required vs optional, valid range).

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 uses a specific verb ('get') and resource ('trivia' about tournaments), with examples that clearly distinguish it from sibling tools like get_tournament or list_tournaments. It defines the tool as providing 'curated factual nuggets' with categories.

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

Usage Guidelines5/5

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

Explicitly states when to use: when the user wants 'interesting facts about 1958' or 'tell me something I don't know about Italia 90'. It also provides a negative guideline by noting it is 'far less hallucination-prone than free-recall about old tournaments', implying when not to use other tools.

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