Skip to main content
Glama

Ai readiness pack

ai_readiness_pack
Read-onlyIdempotent

Audits any public domain and generates ready-to-deploy AI-readiness & security implementation files: tailored /llms.txt, /.well-known/agent-card.json (A2A v1), /.well-known/mcp-server-card.json, DMARC/SPF DNS fixes, nginx/Cloudflare security headers, and deployment guide. $0.05 per call over x402 or X-API-Key. Not advice.

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": "ai_readiness_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesPublic company domain or website URL (e.g. cloudflare.com)
paymentNoOptional x402 payment header value

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered; the description adds materially on top with the $0.05 per-call cost, the two accepted auth mechanisms (x402 payment header or X-API-Key), and a 'Not advice' liability disclaimer. What it does not disclose is how the generated files are returned (inline content vs. references) or whether repeated calls re-audit live state, which is the main remaining behavioral unknown.

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?

Front-loaded with the core action and its deliverable list, then closes with the two facts an agent cannot get from structured fields (price/auth and disclaimer). The artifact enumeration is long but each item is load-bearing because it defines what the call returns; only slight tightening would help.

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?

For a composite, multi-artifact tool with no output schema, the description does the necessary work by listing every artifact produced, which is what an agent needs to decide relevance. The one gap is the return shape — with no output schema, an agent still cannot tell whether it receives file contents, URLs, or a summary report.

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%, so both parameters are already documented in the schema, and the description adds only the qualifier that the domain must be public — which does not appear in the schema text but is easily inferred. No syntax, URL-vs-domain normalization behavior, or payment header format is clarified beyond the schema, so the baseline of 3 applies.

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?

Names a specific verb ('Audits') and resource ('any public domain') and enumerates the concrete deliverables (llms.txt, agent-card.json, mcp-server-card.json, DNS fixes, security headers, deployment guide), so the agent knows exactly what a call produces. It stops short of differentiating itself from overlapping siblings like security_headers, dns_records, or agent_card_grade, leaving the agent to infer this is the bundled/one-shot version.

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

Usage Guidelines3/5

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

Usage is implied by the deliverable list — an agent would reasonably call this to get an AI-readiness package for a domain — and 'any public domain' plus 'Not advice' sets a light scope boundary. However, there is no explicit when-to-use vs when-not guidance and no pointer to the narrower single-purpose siblings that cover a subset of the same checks.

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