Skip to main content
Glama
jbuchan

Accessibility MCP Server

by jbuchan

list_test_results

Retrieve all accessibility test result files to review WCAG compliance reports, violation summaries, and remediation guidance from comprehensive website audits.

Instructions

List all available accessibility test result files

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'list_test_results' MCP tool. It calls fileManager.listTestResults() to get the list of files and formats a numbered list as the tool response.
    private async handleListTestResults(): Promise<CallToolResult> {
      const files = await this.fileManager.listTestResults();
      
      if (files.length === 0) {
        return {
          content: [
            {
              type: 'text',
              text: 'No accessibility test results found.'
            }
          ]
        };
      }
    
      const fileList = files.map((file, index) => `${index + 1}. ${file}`).join('\n');
      
      return {
        content: [
          {
            type: 'text',
            text: `Available test result files:\n\n${fileList}`
          }
        ]
      };
    }
  • Registration of the 'list_test_results' tool in the ListToolsRequestSchema response, including name, description, and input schema.
    {
      name: 'list_test_results',
      description: 'List all available accessibility test result files',
      inputSchema: {
        type: 'object',
        properties: {},
        additionalProperties: false
      }
    }
  • Input schema for the list_test_results tool, defining no required parameters.
    inputSchema: {
      type: 'object',
      properties: {},
      additionalProperties: false
    }
  • Helper method in FileOutputManager that lists test result files by reading the output directory and filtering by filename pattern.
    async listTestResults(): Promise<string[]> {
      try {
        const files = await fs.readdir(this.outputDir);
        return files.filter(file => file.startsWith('accessibility-test-') && file.endsWith('.txt'));
      } catch (error) {
        console.error('Failed to list test results:', error);
        return [];
      }
    }
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 the action ('List all available') but does not explain key traits such as whether this is a read-only operation, if it requires authentication, how results are formatted (e.g., pagination), or any rate limits. This leaves significant gaps in understanding the tool's behavior.

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 with no wasted words. It is front-loaded with the core action and resource, making it highly efficient and easy to parse for an AI agent.

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 lack of annotations and output schema, the description is incomplete for a tool that likely returns a list of files. It does not specify the format of the results (e.g., file names, metadata), any filtering criteria, or error handling. For a list operation, more context on the output is needed to be fully helpful.

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 zero parameters, and the input schema has 100% description coverage (though empty). The description does not need to add parameter details, as there are none to document. It appropriately avoids redundancy, earning a high score 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 ('accessibility test result files'), making the purpose explicit. However, it does not differentiate from sibling tools like 'get_test_results' or 'test_accessibility', which might have overlapping or distinct functionalities, preventing a perfect score.

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 'get_test_results' or 'test_accessibility'. It lacks explicit instructions on context, prerequisites, or exclusions, leaving the agent with minimal usage direction.

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/jbuchan/accessibility-mcp-server'

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