Skip to main content
Glama
chrispickford

fifa-public-api-mcp

list_confederations

Retrieve the six FIFA confederations (UEFA, CONMEBOL, CONCACAF, CAF, AFC, OFC) along with their unique identifiers.

Instructions

List the six FIFA confederations (UEFA, CONMEBOL, CONCACAF, CAF, AFC, OFC), each with its idConfederation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNoReturn FIFA's untouched payload instead of the trimmed shape
languageNoLanguage code passed through to the API and used for name selectionen
Behavior4/5

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

For a simple read-only listing tool, the description conveys the core behavior. It does not disclose authentication needs or idempotency, but the function is straightforward with no hidden traits.

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?

A single sentence that front-loads the purpose with zero wasted words, achieving maximum conciseness.

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 tool's simplicity (no output schema, 2 optional params), the description covers the main function. It could hint at the output structure beyond 'idConfederation', but the parameter descriptions handle the rest.

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 100%, and the tool description adds no extra meaning beyond the schema's parameter descriptions. Baseline score of 3 is appropriate.

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 'list' and the specific resource 'six FIFA confederations' with enumeration, making the tool's purpose unambiguous and distinct from sibling list tools.

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?

No explicit guidance on when to use this tool versus alternatives like list_countries or list_seasons. The description implies usage for listing confederations but lacks exclusions or context.

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/chrispickford/fifa-public-api-mcp'

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