Skip to main content
Glama

royal-mcp__wp_audit_agent_readiness

Read-onlyIdempotent

Read-only: what an AI agent finds when it visits this site, graded on the 0-5 levels the public agent-readiness scanners use (robots.txt and rules for AI bots, content signals, sitemap, markdown for agents, MCP server card, agent skills, WebMCP, API catalog, sign-in discovery). Each check says pass / fail / not checked and what would fix it. Reads the site's own public addresses and changes no content. Requires manage_options. Saves the latest result for the Royal MCP Pro dashboard unless the site or connection is read-only. (site: demo.royalplugins.com) Through Royally: read-only, runs straight away.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "royal-mcp__wp_audit_agent_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idNoSite to run this tool on: 8ef2e52b-bd07-4671-a363-ebe8b480b65c (https://demo.royalplugins.com)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description still adds real value beyond them: it states the required capability (manage_options), discloses a side effect not implied by readOnlyHint (the latest result is persisted for the dashboard unless the site or connection is read-only), and notes that it only reads public addresses. The one gap is what happens when the permission check fails.

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 purpose and scope are front-loaded, and the check list, while dense, is informative rather than filler. The trailing '(site: demo.royalplugins.com) Through Royally: read-only, runs straight away.' is redundant metadata that restates the annotations and could be dropped.

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?

There is no output schema, yet the description explains the return shape well: each check reports pass / fail / not checked plus a remediation hint. Combined with the permission requirement, the read-only/no-content-change guarantee, and the dashboard persistence caveat, an agent has everything needed to call this correctly.

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 coverage is 100% and the single site_id parameter carries a fully documented enum with the resolved site URL, so the schema already does the work. The description adds nothing about parameter meaning, which is acceptable at this coverage level but earns only the baseline.

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 states a concrete verb and resource: it audits how AI agents see the site, graded on a 0-5 scale, and enumerates the exact checks (robots.txt/AI bot rules, content signals, sitemap, markdown for agents, MCP server card, agent skills, WebMCP, API catalog, sign-in discovery). This clearly separates it from sibling SEO audit tools by naming a distinct subject matter.

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?

The context of use is implied by 'what an AI agent finds when it visits this site', which tells the agent to run this for AI-crawler/agent readiness. However, there is no explicit when-to-use vs. when-not, no named alternative (e.g., the SEO audit siblings), and no stated precondition beyond the manage_options requirement.

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