cuporacle-mcp

World Cup fixtures

wc_fixtures

Read-only

Retrieve FIFA World Cup 2026 fixtures for a specific date or get the next upcoming matches, sorted soonest first.

Instructions

List FIFA World Cup 2026 fixtures. Pass a date (YYYY-MM-DD) for that day, or omit to get the next upcoming matches (soonest first). Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wc_fixtures"
  }
}

Input Schema

Name	Required	Description	Default
`date`	No	Optional day filter (UTC), e.g. 2026-07-14. Omit for the next upcoming fixtures.

Output Schema

Name	Required	Description	Default
`count`	Yes
`matches`	Yes
`snapshot`	Yes
`attribution`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 17, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds value by noting the 'soonest first' ordering and the tool being 'Free', without contradicting annotations.

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 short, front-loaded sentences with no extraneous information. Every word earns its place.

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 read-only tool with one optional parameter and an output schema, the description covers all key behaviors: date filtering, default response, and ordering. Output format is handled by the schema.

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 coverage is 100%, so baseline is 3. The description adds meaning by stating the default behavior when date is omitted ('next upcoming') and the format hint (YYYY-MM-DD), going 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?

The description clearly states 'List FIFA World Cup 2026 fixtures' with a specific verb and resource, and distinguishes from sibling tools like wc_bracket and wc_live by focusing on fixture listing.

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?

It explains when to pass a date and what happens when omitted ('next upcoming matches'), but lacks explicit comparison or when-not-to-use advice. Still clear enough for an AI agent.

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

Deploy Server