mcp-fifa-scheduler
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_match_eventB | Create a match event for the match in the world cup and send to the mail of the recipient |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The single tool clearly targets a specific action.
The tool name 'create_match_event' follows a consistent verb_noun pattern, which is clean and predictable, even though there is only one tool.
A single tool for a scheduler server is severely insufficient; even a minimal scheduler would typically require listing, updating, or deleting events. The count feels far too thin for the declared purpose.
The tool only creates a match event and sends an email. There is no way to read, update, cancel, or manage events in any other way, so the surface is severely incomplete for a scheduling domain.