Skip to main content
Glama
zafronix

World Cup History MCP

get_stadium

Look up a World Cup stadium's details using its unique slug. Start with list_stadiums to find the correct slug.

Instructions

Single venue details by stable slug ID. Slugs are kebab-case ("estadio-azteca", "maracana", "wembley-stadium-old", "metlife-stadium"). Use list_stadiums first if you need to discover the right ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesStadium slug, e.g. "estadio-azteca"

Implementation Reference

  • The handler for get_stadium: calls api() with /stadiums/{id} path. It receives a slug ID (kebab-case) and fetches venue details from the API.
    handler: async (args: { id: string }) => api(`/stadiums/${args.id}`),
  • The input schema for get_stadium: expects a single string field 'id' (min 2 chars) describing the stadium slug (e.g. 'estadio-azteca'). The schema is strict (no extra fields).
    schema: z.object({
      id: z.string().min(2).describe('Stadium slug, e.g. "estadio-azteca"'),
    }).strict(),
  • src/index.ts:240-250 (registration)
    The tool registration entry in the 'tools' array. Defines name 'get_stadium', description, schema, and handler. This array is consumed by ListToolsRequestSchema and CallToolRequestSchema handlers.
    {
      name: 'get_stadium',
      description:
        'Single venue details by stable slug ID. Slugs are kebab-case ("estadio-azteca", ' +
        '"maracana", "wembley-stadium-old", "metlife-stadium"). Use list_stadiums first if ' +
        'you need to discover the right ID.',
      schema: z.object({
        id: z.string().min(2).describe('Stadium slug, e.g. "estadio-azteca"'),
      }).strict(),
      handler: async (args: { id: string }) => api(`/stadiums/${args.id}`),
    },
  • The api() helper function that get_stadium's handler delegates to. It constructs the URL, adds auth headers (X-API-Key), fetches data, and returns parsed JSON. Handles errors and missing API key.
    async function api<T = unknown>(path: string): Promise<T> {
      if (!API_KEY) {
        throw new Error(
          'WC_API_KEY is not set in the environment. Get a free key at ' +
          'https://api.zafronix.com/signup and add it to your MCP client ' +
          'config: { "env": { "WC_API_KEY": "zwc_pk_..." } }',
        );
      }
      const url = path.startsWith('http') ? path : `${API_BASE}${path}`;
      const res = await fetch(url, {
        headers: {
          'X-API-Key':  API_KEY,
          'Accept':     'application/json',
          'User-Agent': 'wc-mcp/0.1.2',
        },
      });
      if (!res.ok) {
        const body = await res.text().catch(() => '');
        throw new Error(`API ${res.status} ${res.statusText} on ${path}: ${body.slice(0, 240)}`);
      }
      return res.json() as Promise<T>;
    }
Behavior3/5

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

No annotations provided, so description carries full burden. It explains slug format but does not specify return fields, read-only nature, or any side effects. Adequate but incomplete.

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 concise sentences: first defines purpose and key detail (slug format), second gives usage guidance. No unnecessary words.

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

Completeness3/5

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

No output schema; description could hint at returned fields. However, tool is simple with one parameter and clear ID source, making it adequate for agents.

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?

Schema covers parameter with example and type. Description adds format detail ('kebab-case') and multiple examples, adding value beyond the schema.

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?

Clearly states the tool returns single venue details by slug ID. Uses specific verb 'get' and resource 'venue details', and distinguishes from sibling 'list_stadiums' which discovers IDs.

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 instructs to use 'list_stadiums first if you need to discover the right ID', providing clear context on when to use this tool vs an alternative.

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