Skip to main content
Glama

get_summary

Identify and summarize accessibility issues on any webpage using axe-core. Input the URL to receive a concise report for improving web accessibility and integrating fixes with AI assistants.

Instructions

Get a summary of accessibility issues for a webpage

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL of the webpage to audit

Implementation Reference

  • The main handler function for the 'get_summary' tool. It validates the input URL, launches a Puppeteer browser, loads the page, runs Axe accessibility checker, computes a summary including total issues, breakdown by severity, top 5 issues, and test counts, then returns it as JSON text content.
    async getSummary(args) {
      if (!args.url) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'URL is required'
        );
      }
    
      try {
        const browser = await puppeteer.launch({
          headless: 'new',
          args: ['--no-sandbox', '--disable-setuid-sandbox'],
        });
        const page = await browser.newPage();
        
        // Set a reasonable viewport
        await page.setViewport({ width: 1280, height: 800 });
        
        // Navigate to the page
        await page.goto(args.url, { waitUntil: 'networkidle2', timeout: 30000 });
        
        // Run axe on the page
        const results = await new AxePuppeteer(page).analyze();
        
        // Close the browser
        await browser.close();
        
        // Create a summary
        const summary = {
          url: args.url,
          timestamp: new Date().toISOString(),
          totalIssues: results.violations.length,
          issuesBySeverity: {
            critical: results.violations.filter(v => v.impact === 'critical').length,
            serious: results.violations.filter(v => v.impact === 'serious').length,
            moderate: results.violations.filter(v => v.impact === 'moderate').length,
            minor: results.violations.filter(v => v.impact === 'minor').length,
          },
          topIssues: results.violations
            .sort((a, b) => {
              const impactOrder = { critical: 0, serious: 1, moderate: 2, minor: 3 };
              return impactOrder[a.impact] - impactOrder[b.impact];
            })
            .slice(0, 5)
            .map(violation => ({
              id: violation.id,
              impact: violation.impact,
              description: violation.description,
              helpUrl: violation.helpUrl,
            })),
          passedTests: results.passes.length,
          incompleteTests: results.incomplete.length,
        };
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(summary, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error getting summary: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema definition for the 'get_summary' tool, specifying an object with a required 'url' string property.
    inputSchema: {
      type: 'object',
      properties: {
        url: {
          type: 'string',
          description: 'URL of the webpage to audit',
        },
      },
      required: ['url'],
    },
  • src/index.js:66-79 (registration)
    Tool registration in the ListToolsRequestHandler response, defining name, description, and input schema for 'get_summary'.
    {
      name: 'get_summary',
      description: 'Get a summary of accessibility issues for a webpage',
      inputSchema: {
        type: 'object',
        properties: {
          url: {
            type: 'string',
            description: 'URL of the webpage to audit',
          },
        },
        required: ['url'],
      },
    },
  • src/index.js:87-88 (registration)
    Dispatch registration in the CallToolRequestHandler switch statement, routing calls to the getSummary method.
    case 'get_summary':
      return this.getSummary(request.params.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 fails to describe key behavioral traits such as whether it performs a live scan, uses cached data, requires authentication, has rate limits, or what the output format looks like. This is inadequate for a tool with no annotation coverage.

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 purpose without unnecessary words. It is appropriately sized and front-loaded, with zero waste.

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. It does not explain what the summary includes, how it's formatted, or any behavioral context needed for effective use. For a tool with no structured data support, this leaves significant gaps in understanding.

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 schema description coverage is 100%, with the single parameter 'url' fully documented in the schema. The description adds no additional meaning beyond what the schema provides, such as URL format requirements or validation rules. Baseline 3 is appropriate when the schema does the heavy lifting.

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 tool's purpose with a specific verb ('Get') and resource ('summary of accessibility issues for a webpage'). It distinguishes from the sibling tool 'audit_webpage' by focusing on summary retrieval rather than a full audit, though the distinction could be more explicit.

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 the sibling 'audit_webpage'. It lacks explicit instructions on alternatives, prerequisites, or exclusions, leaving the agent to infer usage from the tool name and description alone.

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

Related 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/priyankark/a11y-mcp'

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