Skip to main content
Glama

Run full AX Audit with simulation and benchmark

run_full_audit
Read-only

Run the full AX Audit on a URL — the same real AR-* checks as scan_site (the exact check count grows over time, so it is intentionally not pinned here), plus an agent-simulation task (e.g. "find pricing") and an industry benchmark percentile, with the result persisted server-side. Returns a report_id that can be used to retrieve the same report later without re-scanning. No authentication required.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "run_full_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL to scan, e.g. https://example.com
industryNoIndustry to benchmark against, e.g. saas. Defaults to "saas".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=true, openWorldHint=true, idempotentHint=false, destructiveHint=false), the description discloses three things the annotations cannot: results are persisted server-side, a report_id is returned as a reusable handle, and no authentication is required. It also warns that the check count grows over time, which prevents an agent from hard-coding expectations. Minor gap: no indication of runtime cost for a simulation-plus-benchmark job, and the server-side persistence sits in slight tension with a read-only hint, though idempotentHint=false is consistent with creating a new report each run.

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?

The core capability and the sibling comparison are front-loaded in the first sentence, with the return value and auth note following in short, purposeful sentences. The parenthetical about the check count not being pinned is slightly defensive but earns its place by preventing stale assumptions. Dense but no filler.

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

Completeness4/5

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

With no output schema, the description carries the return-value burden and does so adequately by naming report_id and its reuse path, and it states the auth requirement. For a two-parameter, open-world scan job, the remaining unknowns are operational (expected duration, any rate limits) rather than correctness-critical, so this is close to complete.

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?

Schema description coverage is 100% for both parameters, so the schema already documents url and industry (including the "saas" default). The description adds only marginal meaning — that industry drives the benchmark percentile — which the schema's own wording ("Industry to benchmark against") largely covers. 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.

Purpose5/5

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

The description gives a specific verb and resource ("Run the full AX Audit on a URL") and explicitly differentiates the tool from its sibling scan_site ("the same real AR-* checks as scan_site ... plus an agent-simulation task ... and an industry benchmark percentile"). It also signals the relationship to get_report by explaining the returned report_id, so an agent can place the tool among its siblings without opening any schema.

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

Usage Guidelines4/5

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

Usage context is clear: this is the heavier, complete audit including simulation and benchmark, and the report_id lets you retrieve results later "without re-scanning," which implicitly routes repeat access to get_report. What is missing is an explicit exclusion — it never says when to prefer the lighter scan_site (e.g., when simulation or benchmarking is not needed), so the agent must infer the trade-off.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources