cuporacle-mcp

World Cup live score

wc_live

Read-only

Retrieve live score, minute, and match status for a World Cup match using its ID. Shows half-time, full-time, or in-play state.

Instructions

Live score, minute and status for one World Cup match by id. Reflects half-time / full-time / in-play state. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "matchId": "<matchId>"
    },
    "name": "wc_live"
  }
}

Input Schema

Name	Required	Description	Default
`matchId`	Yes	football-data match id (from wc_fixtures).

Output Schema

Name	Required	Description	Default
`away`	Yes
`home`	Yes
`score`	Yes
`minute`	Yes
`status`	Yes
`matchId`	Yes
`snapshot`	Yes
`attribution`	Yes
`kickoff_utc`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 17, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description does not need to repeat those. It adds minor context by mentioning 'free' and game states, but does not detail behavior like data freshness, rate limits, or required permissions. With annotations covering safety, a score of 3 is appropriate.

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 (18 words) that front-load the core action: 'Live score, minute and status for one World Cup match by id.' Every word adds value, no fluff or redundancy.

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?

Given the single parameter, clear schema descriptions, readOnlyHint, and an output schema (not shown), the description adequately covers what the tool returns (score, minute, status, states). It mentions 'free' as a minor trait. For a simple live-score retrieval tool, it is sufficiently complete, though lacking explicit mention of authentication or rate limits (likely not required due to openWorldHint).

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?

The input schema already describes matchId as 'football-data match id (from wc_fixtures)' with constraints. The description repeats 'by id' but adds no new meaning. With 100% schema coverage, baseline is 3.

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 provides live score, minute, and status for a single World Cup match by ID. It distinguishes itself from siblings like wc_fixtures (which likely lists matches) by specifying 'for one World Cup match by id' and mentioning game states (half-time, full-time, in-play).

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

Usage Guidelines3/5

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

The description implies usage for retrieving live data for one match but does not explicitly state when to use this tool versus alternatives (e.g., wc_fixtures for fixtures, wc_bracket for bracket). No exclusions or alternative suggestions are provided, leaving the agent to infer from sibling names.

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

Deploy Server