Skip to main content
Glama

argus_audit

Run a fast QA audit on any URL via Chrome DevTools Protocol. Detects JS errors, network failures, SEO issues, and accessibility violations in one pass. Returns findings and summary for CI smoke tests and pre-deploy gates.

Instructions

Fast QA audit on a URL via Chrome DevTools Protocol. Runs 8 analyzers in one pass: JS errors, unhandled rejections, network failures (4xx/5xx), API frequency loops, CSS cascade issues, SEO violations, security header checks, and accessibility. Returns { findings: [{severity, type, message, url}], summary: {critical, warning, info} }. Use for CI smoke tests and pre-deploy gates. Pass cache: true to skip re-crawl on repeat calls to the same URL within a session — useful in tight fix loops. For Lighthouse scoring and memory leak detection, use argus_audit_full. Requires Chrome running with --remote-debugging-port=9222.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFull URL to audit, including protocol and path (e.g. http://localhost:3000/checkout). Must be reachable by the running Chrome instance.
criticalNoWhen true, console.error calls are escalated to critical severity. Set true for business-critical routes (login, checkout, dashboard) where any error is a blocker.
cacheNoWhen true, returns the cached result for this URL if one exists (from a previous argus_audit call in this session) without re-crawling. Use in fix loops to cheaply re-read the last audit while iterating on a fix. Cache is per-session, max 20 entries, LRU eviction.
Behavior5/5

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

Discloses all key behaviors: runs 8 analyzer types, returns findings with severity/type/message/url, explains cache mechanics (per-session, 20 entries, LRU eviction), and even specifies the required Chrome flag. No annotations exist, so description carries full burden and excels.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single paragraph but densely packed with useful information. Could benefit from slight structuring (e.g., bullet points for analyzers), but no unnecessary words; front-loaded with action and purpose.

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

Completeness5/5

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

Covers all critical aspects: input (url + optional params), output format, caching rules, eight specific analyzer categories, and environment prerequisite (Chrome flag). No output schema exists, so description compensates fully.

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

Parameters5/5

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

Each parameter gains meaningful context beyond schema: url reachability, critical for business routes, cache session behavior and eviction policy. Schema coverage is 100%, but description adds operational nuance essential for correct use.

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

Purpose5/5

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

Description clearly states the tool performs a fast QA audit via Chrome DevTools Protocol with 8 specific analyzers. It distinguishes from sibling argus_audit_full by noting that tool covers Lighthouse scoring and memory leak detection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states use cases: 'Use for CI smoke tests and pre-deploy gates.' Provides guidance on caching for fix loops and explicitly advises when to use the sibling tool instead, offering clear usage boundaries.

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/ironclawdevs27/Argus'

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