IPL MCP Server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_ipl_dataC | Query IPL cricket data using natural language. Examples: - 'Show me all matches in the dataset' - 'Which team won the most matches?' - 'Who scored the most runs across all matches?' - 'What was the highest total score?' - 'Show matches played in Mumbai' - 'Who has the best bowling figures?' - 'Show me Virat Kohli batting stats' - 'What's the average first innings score?' - 'Show me all centuries scored' - 'Which venue has the highest scoring matches?' |
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 ambiguity or overlap between tools. The single tool 'query_ipl_data' has a clearly defined purpose that cannot be confused with any other tool in this server.
The single tool name 'query_ipl_data' follows a clear verb_noun pattern. With only one tool, naming consistency is inherently perfect as there are no other tools to compare against or create inconsistencies with.
A single tool for an IPL cricket data server feels too thin for the apparent scope. The examples suggest complex queries about matches, players, venues, and statistics, which would typically require multiple specialized tools for a complete interface. One tool attempting to handle all these diverse queries through natural language is insufficient for proper domain coverage.
The server appears to cover IPL cricket data, but with only one natural language query tool, the surface is severely incomplete. There are no dedicated tools for specific operations like retrieving match details, player statistics, team information, or venue data. The single tool approach creates significant gaps that will likely cause agent failures when trying to perform structured operations.