Skip to main content
Glama
abaiii168

World Cup 2026 MCP Server

by abaiii168

Get World Cup 2026 Matches

get_world_cup_2026_matches

Fetch World Cup 2026 match fixtures filtered by stage, group, or team, with times converted to your chosen time zone.

Instructions

Return World Cup 2026 fixtures in a requested IANA time zone, optionally filtered by stage, group, or team code/name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timezoneNoIANA time zone, for example Europe/London or America/New_York. Defaults to UTC.
stageNo
groupNoGroup letter A-L for group-stage filtering.
teamNoTeam code or English team name, for example MEX, BRA, Japan, or United States.
limitNoMaximum number of matches to return.
Behavior3/5

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

No annotations exist, so description carries full burden. It mentions time zone conversion but omits other behavioral traits like data freshness, error conditions, or if results are static. Adequate but not comprehensive.

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?

Single sentence of 18 words, front-loaded with purpose, no fluff. Efficiently communicates core functionality.

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 and moderate complexity. Description covers filtering but does not hint at return format, ordering, or data volume. Could be improved with brief note on match object fields.

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 80%, so parameters are mostly documented. The description adds little beyond restating filter options; it confirms time zone handling already implied by parameter descriptions. No new semantics.

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 the verb 'Return' and the resource 'fixtures' with specific filters (time zone, stage, group, team). It distinguishes from siblings like get_world_cup_2026_match (singular) and get_world_cup_2026_dataset (broader).

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 when to use (for filtered match list), but does not explicitly state when not to use or mention alternatives among siblings. Some guidance on selecting this tool over others is missing.

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/abaiii168/world-cup-2026-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server