Skip to main content
Glama

list-sections

Lists all documentation sections for Macroforge to help users find relevant information by analyzing use cases and categories before retrieving specific documentation.

Instructions

Lists all Macroforge documentation sections.

Returns sections with:

  • title: Section name

  • use_cases: When this doc is useful (comma-separated keywords)

  • path: File path

  • category: Category name

WORKFLOW:

  1. Call list-sections FIRST for any Macroforge-related task

  2. Analyze use_cases to find relevant sections

  3. Call get-documentation with ALL relevant section names

Example use_cases: "setup, install", "serialization, json", "validation, email"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The primary handler function that implements the logic for the 'list-sections' tool. It filters the cached documentation sections to show only top-level sections (excluding sub-chunks), formats them with title, use_cases, path, and category, and returns a formatted text response.
    function handleListSections() {
      // Filter out sub-chunks (sections with parent_id) - only show top-level sections
      const topLevelSections = sections.filter((s) => !s.parent_id);
    
      const formatted = topLevelSections
        .map(
          (s) =>
            `* title: [${s.title}], use_cases: [${s.use_cases}], path: [${s.path}], category: [${s.category_title}]`
        )
        .join('\n');
    
      return {
        content: [
          {
            type: 'text' as const,
            text: `Available Macroforge documentation sections:\n\n${formatted}`,
          },
        ],
      };
    }
  • The registration of the 'list-sections' tool in the ListToolsRequestSchema handler, providing the tool's name, detailed description of its purpose and workflow, and inputSchema (empty object as the tool takes no parameters).
            {
              name: 'list-sections',
              description: `Lists all Macroforge documentation sections.
    
    Returns sections with:
    - title: Section name
    - use_cases: When this doc is useful (comma-separated keywords)
    - path: File path
    - category: Category name
    
    WORKFLOW:
    1. Call list-sections FIRST for any Macroforge-related task
    2. Analyze use_cases to find relevant sections
    3. Call get-documentation with ALL relevant section names
    
    Example use_cases: "setup, install", "serialization, json", "validation, email"`,
              inputSchema: {
                type: 'object',
                properties: {},
              },
            },
  • The input schema definition for the 'list-sections' tool, specifying an empty object since no input parameters are required.
    inputSchema: {
      type: 'object',
      properties: {},
    },
  • The dispatch case in the CallToolRequestSchema handler that routes 'list-sections' tool calls to the handleListSections function.
    case 'list-sections':
      return handleListSections();
  • src/index.ts:79-79 (registration)
    Invocation of registerTools which sets up all tool handlers and registrations, including for 'list-sections'.
    registerTools(server);
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the return format (title, use_cases, path, category) and workflow behavior, but lacks details on potential limitations like pagination, error handling, or performance characteristics. It doesn't contradict any annotations.

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 well-structured with clear sections (description, returns, workflow, example), front-loaded with the core purpose, and every sentence adds value without redundancy. It efficiently communicates necessary information.

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

Completeness4/5

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

Given 0 parameters, no annotations, and no output schema, the description provides good context by detailing the return structure and workflow. However, it could be more complete by mentioning any prerequisites (e.g., authentication) or limitations, though the lack of complexity keeps it adequate.

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?

The input schema has 0 parameters with 100% coverage, so the baseline is 4. The description appropriately adds no parameter information, as none are needed, and focuses on output semantics instead.

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

Purpose5/5

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

The description clearly states the verb 'Lists' and the resource 'all Macroforge documentation sections', making the purpose specific and unambiguous. It distinguishes this tool from siblings like 'get-documentation' by focusing on listing sections rather than retrieving content.

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

Usage Guidelines5/5

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

The WORKFLOW section provides explicit guidance: 'Call list-sections FIRST for any Macroforge-related task', followed by steps for analysis and calling 'get-documentation'. It clearly states when to use this tool versus alternatives, with a named sibling tool mentioned.

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/macroforge-ts/mcp-server'

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