Skip to main content
Glama

Agent launch audit

agent_launch_audit
Read-onlyIdempotent

Comprehensive 1-call production launch readiness audit for any AI agent, MCP server, or x402 API domain: fuses A2A/MCP/x402/JWKS/llms.txt discovery grading, HTTPS/phishing threat checks, tech-stack detection, and optional live x402 delivery probe, returning prioritized revenue/discovery fixes and an Ed25519-signed LaunchReadinessCertificate verifiable offline via /.well-known/jwks.json. $0.02 per call over x402 or X-API-Key. Call once without payment for terms, then call again with payment.

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": {
      "domain": "<domain>"
    },
    "name": "agent_launch_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain or URL of the AI agent / MCP server / x402 API to audit (e.g. agent402.tools).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).
x402_urlNoOptional specific x402 endpoint URL on that domain to live-probe for delivery-score.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnly/openWorld/idempotent/non-destructive), the description discloses the paywall ($0.02 per call over x402 or X-API-Key), the two-phase handshake required to get terms before paying, and the return artifact — an Ed25519-signed LaunchReadinessCertificate verifiable offline via /.well-known/jwks.json. None of that is in the annotations or schema, and it materially changes how an agent must sequence the call.

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?

Content is front-loaded — capability, then return value, then pricing, then call sequence — and no sentence is filler. The first sentence is a dense run-on packed with acronyms, so the structure is efficient but not maximally scannable.

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?

For a high-complexity, unannotated-output tool with no output schema, the description covers everything an agent needs before calling: what is checked, what is returned, the certificate's verifiability, the price, and the required two-call payment sequence. Error and failure behavior is the only notable omission, and the schema fully documents the inputs.

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?

Schema coverage is 100%, so the baseline is 3; the description lifts it by explaining that `payment` participates in a second-call flow after an initial terms call, which the schema only describes as a 'signed x402 payment payload'. It also frames `x402_url` as the optional live delivery probe, adding intent beyond the schema's mechanical wording.

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 ('production launch readiness audit for any AI agent, MCP server, or x402 API domain') and enumerates exactly what is fused into the result (A2A/MCP/x402/JWKS/llms.txt discovery grading, HTTPS/phishing checks, tech-stack detection, optional delivery probe). That scope statement implicitly but clearly separates it from contract_audit, package_audit, or agent_card_grade, which target narrower artifacts.

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?

It gives an explicit invocation protocol: 'Call once without `payment` for terms, then call again with `payment`', plus the cost and payment channels, which resolves the main ambiguity about how to start. It does not, however, state when to prefer this over sibling graders like agent_card_grade or agent_trust, or when a launch-readiness audit is unnecessary.

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