Skip to main content
Glama
90barricade93

MSFS SDK MCP Server

list_categories

Retrieve all available documentation categories from the Microsoft Flight Simulator SDK to organize and access technical resources.

Instructions

List all available MSFS SDK documentation categories

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function implementing the list_categories tool logic, returning available documentation categories.
    async listCategories(): Promise<{ content: Array<{ type: string; text: string }> }> {
      const categoriesList = [
        '- **contents**: Search in documentation contents',
        '- **index**: Search in documentation index',
        '- **glossary**: Search in documentation glossary',
        '- **all**: Search in all categories (default: index)',
      ].join('\n');
    
      return {
        content: [
          {
            type: 'text',
            text: `Available MSFS SDK Documentation Categories:\n\n${categoriesList}\n\nUsage examples:\n- Search for "livery" in all categories: use category "all" or "index"\n- Search for "livery" in contents: use category "contents"\n- Search for "livery" in glossary: use category "glossary"`,
          },
        ],
      };
    }
  • src/index.ts:81-88 (registration)
    Tool registration including name, description, and input schema in the ListToolsRequestHandler.
    {
      name: 'list_categories',
      description: 'List all available MSFS SDK documentation categories',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • src/index.ts:146-147 (registration)
    Dispatch handler in the main switch for direct tool calls.
    case 'list_categories':
      return await this.documentationService.listCategories();
  • src/index.ts:176-177 (registration)
    Dispatch handler in the natural_language_query tool switch.
    case 'list_categories':
      return await this.documentationService.listCategories();
  • Helper function in NaturalLanguageService that parses natural language input to invoke list_categories tool.
    // Match "List categories"
    if (command.toLowerCase() === "list categories") {
      return {
        tool: "list_categories",
        arguments: {}
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't describe how it behaves—e.g., whether it returns a paginated list, the format of the output, or any rate limits. This leaves gaps in understanding the tool's operation.

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, clear sentence that directly states the tool's purpose without any unnecessary words. It's front-loaded and efficient, making it easy to understand at a glance.

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 adequate but minimal. It covers the basic purpose but lacks details on output format or behavioral context, which could be helpful for an agent to use it effectively, though not strictly required for such a straightforward tool.

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 tool has 0 parameters, and the schema description coverage is 100%, so there's no need for parameter details in the description. The description appropriately doesn't mention parameters, aligning with the schema, which justifies a baseline score of 4 for this dimension.

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 ('all available MSFS SDK documentation categories'), making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from its sibling 'list_category_items', which might list items within categories rather than the categories themselves.

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?

The description provides no guidance on when to use this tool versus alternatives like 'list_category_items' or 'search_msfs_docs'. It lacks context about prerequisites, such as whether this is a starting point for documentation navigation or if it requires authentication.

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/90barricade93/MSFS-SDK-MCP'

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