rulebook-mcp
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_rulesB | Search the 2026-27 NBA playing rules. Returns the most relevant sections with ids and an excerpt. |
| get_sectionA | Full text of one rulebook section by id, e.g. 'R14-V' (Rule 14, Section V) or 'C-II-L' (Comments). |
| list_sectionsA | The rulebook's table of contents: every section id with its title. |
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 3 tools
The three tools have clearly distinct roles: search for relevance-based discovery, get_section for fetching full text by known id, and list_sections for browsing the table of contents. An agent can easily choose between them based on whether it needs search, direct retrieval, or an index.
All tool names follow a consistent snake_case verb_noun pattern: search_rules, get_section, list_sections. Singular/plural usage is also coherent with each operation's object.
Three tools are well-scoped for a read-only rulebook reference server. Each tool supports a distinct access pattern—search, browse, and retrieve—without unnecessary surface area.
The surface covers the full read-only lifecycle for this domain: discover sections via list_sections, find relevant content via search_rules, and retrieve full text via get_section. No obvious operational gaps exist for a rulebook reference tool.