Skip to main content
Glama
90barricade93

MSFS SDK MCP Server

list_category_items

Retrieve documentation items from Microsoft Flight Simulator SDK categories to access structured development resources.

Instructions

Returns all items for a given documentation category

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYesCategory to list items from (index, contents, or glossary)

Implementation Reference

  • The core handler function that implements the 'list_category_items' tool. It validates the category, uses embedded data for index/contents/glossary, and returns a formatted text list of items.
    async listCategoryItems(category: string): Promise<{ content: Array<{ type: string; text: string }> }> {
      const validCategories = ['index', 'contents', 'glossary'];
      if (!validCategories.includes(category)) {
        throw new Error(`Invalid category: ${category}. Must be one of: ${validCategories.join(', ')}`);
      }
    
      // Embedded data - geen externe bestanden nodig!
      const categoryData = {
        index: [
          'Introduction',
          'SDK Contents',
          'SDK Overview',
          'Using The SDK',
          'SDK EULA',
          'Release Notes',
          'Samples, Schemas, Tutorials and Primers',
          'Developer Mode',
          'Menus',
          'The Project Editor',
          'The Scenery Editor',
          'The Material Editor',
          'The Script Editor',
          'The Aircraft Editor',
          'Aircraft Debug Menu',
          'The Aircraft Tab',
          'The Flight Model Tab',
          'The AI Tab',
          'The Cockpit Tab',
          'The Gameplay Tab',
          'The Engines Tab',
          'The Systems Tab',
          'The Cameras Tab',
          'The Custom Parameters Tab',
          'The Visual Effects Editor',
          'External Asset Creation',
          'Content Configuration',
          'Programming APIs',
          'Additional Information',
          'How To Create An Aircraft',
          'World Hub'
        ],
        contents: [
          'Introduction',
          'SDK Contents',
          'SDK Overview',
          'Using The SDK',
          'SDK EULA',
          'Release Notes',
          'Samples, Schemas, Tutorials and Primers',
          'Developer Mode',
          'Menus',
          'The Project Editor',
          'The Scenery Editor',
          'The Material Editor',
          'The Script Editor',
          'The Aircraft Editor',
          'Aircraft Debug Menu',
          'The Aircraft Tab',
          'The Flight Model Tab',
          'The AI Tab',
          'The Cockpit Tab',
          'The Gameplay Tab',
          'The Engines Tab',
          'The Systems Tab',
          'The Cameras Tab',
          'The Custom Parameters Tab',
          'The Visual Effects Editor',
          'External Asset Creation',
          'Content Configuration',
          'Programming APIs',
          'Additional Information',
          'How To Create An Aircraft',
          'World Hub'
        ],
        glossary: [
          'ADC',
          'add-ons',
          'ADF',
          'ADI',
          'ADPCM',
          'AFM',
          'AGL',
          'AH',
          'AHRS',
          'ambisonic',
          'AMSL',
          'AoA',
          'AOC',
          'API',
          'APU',
          'ATC',
          'BGL',
          'bpp',
          'Camber',
          'CAS',
          'CFD',
          'CG',
          'CGL',
          'Chord',
          'CoL',
          'dB',
          'dBTP',
          'DDS',
          'de-crab',
          'DEM',
          'Dihedral',
          'DME',
          'DoF',
          'DRM',
          'EAS',
          'ECU',
          'EGT',
          'ELT',
          'EPR',
          'FAF',
          'FIS',
          'FL',
          'flaps',
          'FLC',
          'FOV',
          'FSUIPC',
          'ft',
          'ftlbs',
          'GA',
          'Gallon',
          'GDI+',
          'glTF',
          'GPS',
          'GPWS',
          'GUID',
          'hp',
          'hPa',
          'IAF',
          'IAS',
          'ICAO',
          'ICAO code',
          'ICU',
          'IFR',
          'ILS',
          'Incidence',
          'inHg',
          'ISA',
          'ITT',
          'kcas',
          'kias',
          'Knot',
          'ktas',
          'lbf',
          'lbs',
          'LDA',
          'LKFS',
          'LOD',
          'LU',
          'MAC',
          'Mach',
          'Makefile',
          'MFD',
          'MOI',
          'mph',
          'MSL',
          'MTOW',
          'N1',
          'N2',
          'NDB',
          'nm',
          'OOI',
          'OSM',
          'Oswald Efficiency Factor',
          'Pa',
          'pbh',
          'PBR',
          'PCM',
          'Percent Over 100',
          'PFD',
          'PID',
          'POH',
          'POI',
          'psf',
          'psi',
          'quadkey',
          'Rankine',
          'RNAV',
          'ROC',
          'RPM',
          'RTO',
          'RTPC',
          'SDF',
          'slug',
          'Slug sqft',
          'sqft',
          'STOL',
          'Sweep',
          'Tacan',
          'TAS',
          'TCAS',
          'TIN',
          'TOGA',
          'Twist',
          'UI',
          'VASI',
          'VFR',
          'VFS',
          'VMO',
          'VOR',
          'WASM',
          'WEP',
          'Zulu Time'
        ]
      };
    
      const items = categoryData[category as keyof typeof categoryData];
      
      return {
        content: [
          {
            type: 'text',
            text: items.join('\n')
          }
        ]
      };
    }
  • src/index.ts:103-117 (registration)
    Tool registration in the ListToolsRequestHandler, defining the name, description, and input schema for 'list_category_items'.
    {
      name: 'list_category_items',
      description: 'Returns all items for a given documentation category',
      inputSchema: {
        type: 'object',
        properties: {
          category: {
            type: 'string',
            description: 'Category to list items from (index, contents, or glossary)',
            enum: ['index', 'contents', 'glossary']
          }
        },
        required: ['category']
      }
    }
  • Input schema definition for the 'list_category_items' tool, specifying the required 'category' parameter with allowed enum values.
    inputSchema: {
      type: 'object',
      properties: {
        category: {
          type: 'string',
          description: 'Category to list items from (index, contents, or glossary)',
          enum: ['index', 'contents', 'glossary']
        }
      },
      required: ['category']
    }
  • Helper routing code in the CallToolRequestHandler switch statement that validates input and delegates to the documentationService handler.
    case 'list_category_items':
      if (!args?.category) {
        throw new Error('Category parameter is required');
      }
      return await this.documentationService.listCategoryItems(String(args.category));
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'Returns all items,' implying a read-only operation, but doesn't specify if it's paginated, the format of returned items, potential rate limits, or error conditions. This leaves significant gaps in understanding how the tool behaves beyond its basic function.

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 directly states the tool's function without unnecessary words. It is front-loaded with the core action and resource, making it easy to parse quickly, which is ideal for conciseness in tool descriptions.

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

Completeness2/5

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

Given the tool's simplicity (1 parameter, no output schema, no annotations), the description is minimal. It lacks details on return values (e.g., item format, list structure), error handling, or integration with sibling tools, making it incomplete for effective agent use despite the straightforward schema.

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

Parameters3/5

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

The input schema has 100% description coverage, clearly documenting the 'category' parameter with an enum of allowed values. The description adds no additional semantic context beyond what the schema provides, such as examples of what 'items' entail or how categories relate to documentation structure, so it meets the baseline for high schema coverage.

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 ('Returns') and resource ('all items for a given documentation category'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'list_categories' (which likely lists categories rather than items within them) or 'get_doc_content' (which might fetch specific document content), leaving room for improvement in sibling distinction.

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. It doesn't mention prerequisites, such as needing a valid category from 'list_categories', or compare it to siblings like 'search_msfs_docs' for more targeted queries, leaving the agent without contextual usage cues.

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