Volleyball 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_queryB | |
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 tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'execute_query' follows a clear verb_noun pattern.
One tool is too few for a server named 'Volleyball MCP Server', which suggests a domain that would typically require multiple operations (e.g., querying players, matches, statistics). A single SQL execution tool feels thin and under-scoped for this apparent purpose.
The tool surface is severely incomplete for a volleyball domain. It only provides raw SQL execution, lacking any domain-specific operations like retrieving player stats, match results, or team information, which would be expected for such a server.