Skip to main content
Glama

check_site_readiness

Check how ready a website is for AI agent interaction. Returns an AI readiness score and breakdown.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe website URL to check (e.g. https://example.com)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. "Check" implies a read-only operation and the second sentence discloses the return shape (score plus breakdown), which is valuable given there is no output schema, but nothing is said about live fetching, latency, rate limits, or auth requirements for a tool that clearly reaches out to an external 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?

Two short sentences with no filler, and the core purpose is front-loaded before the return-value note. Nothing needs trimming, though the brevity leaves obvious questions unaddressed.

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

Completeness3/5

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

For a single-parameter tool with no output schema, the description does well to explain what comes back (score plus breakdown). It is still thin on operational behavior — whether the check is live, how long it takes, and how it relates to the registration/verification siblings — so it is adequate rather than 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 coverage is 100% and the single `url` parameter already carries a format and an example, so the description adds no syntax or format meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting on a one-parameter tool.

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?

"Check how ready a website is for AI agent interaction" gives a specific verb and resource, and defines what "readiness" means (suitability for AI agent interaction), which separates it from verify_site or site_status. It stops short of explicitly naming a sibling to contrast with, so the differentiation is inferential rather than stated.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no mention of how this differs from the sibling tools verify_site, site_status, or register_site. An agent must guess whether a site needs to be registered first or whether this duplicates site_status.

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