Send Your Agent Website Readiness

Explain AI Readiness Score

explain_readiness_score

Read-onlyIdempotent

Explain what an SYA structural readiness score means and the appropriate next step. This does not measure AI answer rankings, mentions, citations or traffic.

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": {
      "score": "<score>"
    },
    "name": "explain_readiness_score"
  }
}

Input Schema

Name	Required	Description	Default
`score`	Yes	SYA structural readiness score from 0 to 100

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 15, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=true and idempotentHint=true, so the agent knows this is a safe, non-destructive operation. The description adds that the tool explains and provides a next step, but no additional behavioral details (e.g., rate limits, auth) are disclosed. The description adds some value beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences: the first defines the purpose, the second clarifies scope. Every word adds value with no redundancy. It is front-loaded with the core action.

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 explanatory tool with one parameter and no output schema, the description is largely complete. It indicates the tool explains meaning and next step. However, it could be slightly more specific about the output format (e.g., returns a text explanation).

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%, with the parameter already well-documented as a number from 0 to 100. The description does not add extra meaning about the parameter beyond what the schema provides, so baseline score of 3 applies.

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 clearly states the tool explains an SYA structural readiness score and its next step, with a specific verb ('Explain') and resource ('readiness score'). It explicitly distinguishes itself by stating what it does not measure (AI answer rankings, mentions, etc.), setting it apart from potential sibling tools.

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?

The description provides clear negative guidance on what the tool does not do (measure AI answer rankings, mentions, citations, traffic), helping the agent avoid misuse. While it lacks explicit 'when to use' or alternatives, the sibling tools are distinctly different actions, making the usage context clear.

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

All Send Your Agent Website Readiness tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?