Skip to main content
Glama
nfodor

Chromium ARM64 Browser

by nfodor

run_best_practices_audit

Audit web pages for performance, accessibility, and SEO best practices using Chromium on ARM64 devices to identify and resolve common issues.

Instructions

Run a best practices audit on the current page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that executes the 'run_best_practices_audit' tool. It ensures the Chromium instance is running, injects JavaScript via CDP to audit the page for best practices (HTTPS usage, mixed HTTP content, deprecated HTML tags, viewport meta tag presence), parses the results, and returns a formatted text response.
    async runBestPracticesAudit() {
      await this.ensureChromium();
      
      const result = await this.sendCDPCommand('Runtime.evaluate', {
        expression: `
          const results = [];
          if (location.protocol !== 'https:') {
            results.push('Page is not served over HTTPS');
          }
          
          const httpResources = Array.from(document.querySelectorAll('[src], [href]'))
            .filter(el => (el.src || el.href)?.startsWith('http:'))
            .length;
          
          if (httpResources > 0) {
            results.push(\`Found \${httpResources} HTTP resources on HTTPS page\`);
          }
          
          const deprecatedTags = Array.from(document.querySelectorAll('font, center, big, small, tt')).length;
          if (deprecatedTags > 0) {
            results.push(\`Found \${deprecatedTags} deprecated HTML tags\`);
          }
          
          const viewport = document.querySelector('meta[name="viewport"]');
          if (!viewport) {
            results.push('Missing viewport meta tag for mobile optimization');
          }
          
          JSON.stringify(results.length > 0 ? results : ['Best practices checks passed']);
        `,
        returnByValue: true
      });
      
      const bestPracticesResults = JSON.parse(result.result?.value || '[]');
      
      return {
        content: [{ type: 'text', text: `Best Practices Audit Results:\\n${bestPracticesResults.join('\\n')}` }],
      };
    }
  • index.js:304-310 (registration)
    Registers the 'run_best_practices_audit' tool in the list of available tools returned by ListToolsRequestSchema, including its name, description, and input schema (empty object, no required parameters).
      name: 'run_best_practices_audit',
      description: 'Run a best practices audit on the current page',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Dispatch case in the CallToolRequestSchema handler that routes calls to 'run_best_practices_audit' to the runBestPracticesAudit method.
    case 'run_best_practices_audit':
      return await this.runBestPracticesAudit();
  • Input schema for the tool: an empty object (no properties or required fields).
    inputSchema: {
      type: 'object',
      properties: {},
    },
Behavior2/5

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

With no annotations, the description carries full burden but lacks behavioral details. It mentions running an audit but doesn't disclose what the audit does (e.g., checks, outputs, or effects), whether it's read-only or modifies state, or any performance or permission considerations, leaving key traits unclear.

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, direct sentence with no wasted words, clearly stating the action and target. It's appropriately sized and front-loaded, making it efficient and easy to parse.

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 complexity of an audit tool with no annotations or output schema, the description is incomplete. It doesn't explain what the audit entails, what results to expect, or how it differs from other audit tools, failing to provide sufficient context for effective use.

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 with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add param info, but this is acceptable given the lack of inputs, aligning with the baseline for zero parameters.

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

Purpose3/5

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

The description states the action ('Run a best practices audit') and target ('on the current page'), which is clear but vague. It doesn't specify what 'best practices' entails or distinguish it from sibling audit tools like accessibility, SEO, or performance audits, leaving the purpose somewhat ambiguous.

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?

No guidance is provided on when to use this tool versus alternatives like run_accessibility_audit or run_seo_audit. The description implies usage on a current page but doesn't specify prerequisites, exclusions, or contextual triggers, offering minimal 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/nfodor/mcp-chromium-arm64'

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