Skip to main content
Glama
Golrigames

Roller Derby Rules MCP Server

by Golrigames

list_sections

Browse all available sections in the French Roller Derby rulebook to locate specific rules on game parameters, scoring, penalties, and officiating.

Instructions

List all available rules sections

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The asynchronous handler function for the 'list_sections' tool. It returns a JSON-formatted list of all available rules sections using the predefined SECTIONS array.
    async () => {
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              SECTIONS.map((s) => ({ id: s.id, name: s.name })),
              null,
              2
            ),
          },
        ],
      };
    }
  • index.js:107-128 (registration)
    The server.registerTool call that registers the 'list_sections' tool, including its name, schema, and handler function.
    // Tool: list_sections
    server.registerTool(
      "list_sections",
      {
        description: "List all available rules sections",
        inputSchema: {},
      },
      async () => {
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(
                SECTIONS.map((s) => ({ id: s.id, name: s.name })),
                null,
                2
              ),
            },
          ],
        };
      }
    );
  • The input schema and description for the 'list_sections' tool. Note that inputSchema is empty as the tool takes no parameters.
    {
      description: "List all available rules sections",
      inputSchema: {},
    },
  • The SECTIONS constant array defining all available rules sections, which is mapped and returned by the list_sections tool handler.
    const SECTIONS = [
      { id: "00-introduction", name: "Introduction", file: "00-introduction.md" },
      {
        id: "01-parametres",
        name: "Match parameters and safety",
        file: "01-parametres.md",
      },
      { id: "02-le-jeu", name: "The game", file: "02-le-jeu.md" },
      { id: "03-score", name: "Score", file: "03-score.md" },
      { id: "04-penalites", name: "Penalties", file: "04-penalites.md" },
      { id: "05-arbitrage", name: "Officiating", file: "05-arbitrage.md" },
    ];
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It states the action but doesn't disclose behavioral traits such as whether this is a read-only operation, potential rate limits, authentication needs, or what format the list returns. This leaves significant gaps for a tool with no structured safety hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core action ('List all available rules sections') with zero wasted words. It's appropriately sized for a simple tool with no parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate but lacks completeness. It doesn't explain return values or behavioral context, which is a gap since no output schema exists to cover that. However, for a basic list operation, it meets the minimum viable threshold.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0 parameters and 100% schema description coverage, the schema already fully documents the input (none). The description adds no parameter information, which is appropriate here. A baseline of 4 is given since no parameters exist, and the description doesn't need to compensate for any gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('List') and resource ('rules sections') with the scope 'all available', making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'search_rules' or 'get_section', which would require more specific scope or filtering details.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'search_rules' or 'get_section'. The description implies a comprehensive listing without filtering, but this isn't stated explicitly, leaving the agent to infer usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Golrigames/RollerDerbyRulesMcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server