Skip to main content
Glama
Sign In
Agent Readiness MCP

Agent Readiness MCP

by forgemeshlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get a prioritized ASO fix plan

get_fix_plan

Scans a website to generate a prioritized remediation plan for agent readiness, including fix points and artifact templates.

Instructions

Scan a site and return a prioritized remediation plan: which signals to add first, the ASO Score points each fix is worth, and ready-to-paste artifact templates (robots.txt AI rules, llms.txt, agent.json, A2A agent-card.json, MCP server card, x402 manifest, pricing.json, security.txt, status endpoint). Use this when the user wants an implementation roadmap or copy-paste fixes; use scan_site when they need full evidence and per-check scoring, and use check_signal to verify one completed fix.

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

Input Schema

NameRequiredDescriptionDefault
urlYesWebsite URL or domain to plan fixes for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. 'Scan a site' implies read-only but doesn't explicitly state safety, side effects, or authorization needs. Lacks explicit disclosure that it does not modify the site.

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?

Relatively concise single sentence front-loading purpose, followed by usage guidance. Slight run-on but no wasted words.

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 simple tool (1 param, no output schema), description covers output contents (plan, points, templates) and provides alternatives. Lacks only explicit safety behavior, but otherwise 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?

Only one parameter (url) with schema coverage 100%. Description does not add extra semantic beyond schema's 'Website URL or domain to plan fixes for'. Baseline 3 is appropriate.

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?

Clearly states verb and resource: 'Scan a site and return a prioritized remediation plan'. Distinguishes from siblings by naming alternatives (scan_site, check_signal) and their use cases.

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 tells when to use this tool vs alternatives: 'Use this when the user wants an implementation roadmap or copy-paste fixes; use scan_site when they need full evidence...'.

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

Deploy Server

Other Tools