xfix

Check page text without JavaScript

check_page_readability

Read-only

Fetches the public page at the given URL without running JavaScript and reports whether its main text is present in the HTML. Checks one page only. Use when the user asks whether a page's content can be read without JavaScript.

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_page_readability"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	The full address of one public page, for example https://example.com/page.

Output Schema

Name	Required	Description	Default
`url`	Yes
`tool`	Yes
`cached`	Yes
`limits`	Yes
`status`	Yes
`verdict`	Yes
`findings`	Yes
`checked_at`	Yes
`report_url`	Yes
`readability`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 19, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint, destructiveHint=false, openWorldHint), so the bar is lower, and the description adds meaningful operational context: no JavaScript execution, single-page scope, and public pages only (implying no authenticated fetches). It does not mention rate limits or failure modes, but the added context is substantive.

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?

Three short sentences, zero filler, with the core behavior (no JS, text presence) front-loaded ahead of the usage trigger. Every sentence earns its place.

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?

The tool is simple (one param, one page, output schema present so return values need no explanation), and the description covers behavior, scope limits, and when to invoke it. Nothing an agent needs to call it correctly is missing.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents the url including format and an example. The description only restates the 'public page' constraint, adding no syntax or constraint detail beyond the schema. Baseline 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?

States a specific verb and resource ('Fetches the public page ... without running JavaScript') plus the exact result reported ('whether its main text is present in the HTML'). It is clearly distinguishable from crawl-style siblings, though it never names an alternative sibling explicitly.

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?

Gives an explicit trigger condition: 'Use when the user asks whether a page's content can be read without JavaScript.' It also scopes usage to a single page ('Checks one page only'), but offers no when-not guidance or comparison against siblings like check_page_visibility.

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

All xfix 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?