Roller Derby Rules 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 |
|---|---|
| list_sectionsB | List all available rules sections |
| get_sectionB | Get the complete content of a specific rules section |
| search_rulesB | Search Roller Derby rules by keyword |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| complete-rules | Complete document containing all rules |
| 00-introduction | Section: Introduction |
| 01-parametres | Section: Match parameters and safety |
| 02-le-jeu | Section: The game |
| 03-score | Section: Score |
| 04-penalites | Section: Penalties |
| 05-arbitrage | Section: Officiating |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: list_sections enumerates available sections, get_section retrieves full content of a specific section, and search_rules performs keyword-based searches across rules. There is no overlap or ambiguity in their functions.
All tool names follow a consistent verb_noun pattern (list_sections, get_section, search_rules) with clear, descriptive verbs and nouns. No deviations or mixed conventions are present.
With 3 tools, the server is well-scoped for its purpose of accessing Roller Derby rules. Each tool earns its place by covering essential operations: listing, retrieving, and searching rules, which is appropriate for a focused domain.
The tool set provides complete coverage for the domain of accessing Roller Derby rules: list_sections for discovery, get_section for detailed retrieval, and search_rules for keyword-based queries. There are no obvious gaps in the surface for this purpose.