Johto Data

Johto Data Page Structured Extract

page_structured_extract

Read-only

Screenshot-free structured extract: title, meta description, price candidates, tables and JSON-LD from server HTML. Costs $0.05 USDC per call via x402. Without payment, the call returns the x402 payment requirements; retry with an X-PAYMENT or PAYMENT-SIGNATURE header, or params._meta["x402/payment"].

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Authorized public page URL

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.2/5.0

Behavior5/5

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

It is exceptionally transparent regarding operational behavior by detailing the cost ($0.05), the payment failure state (returning requirements), and the exact retry mechanics (headers or params). This high-level operational context is invaluable for an agent.

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 dense but highly efficient, front-loading the primary function before detailing the operational cost and failure modes. There is no wasted language.

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?

Because there is no output schema, the description must list the extractable elements, which it does comprehensively. It only misses defining the exact format (e.g., markdown vs. JSON) of tables and price candidates.

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?

Since schema coverage is 100%, the baseline is 3. The description adds minor context by specifying the URL must be an 'Authorized public page URL.'

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 explicitly defines the function as a 'Screenshot-free structured extract' and lists the specific data points extracted (title, meta description, price candidates, tables, and JSON-LD). This is highly specific and distinguishes it from general content extraction siblings.

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 tool does not explicitly state the functional use case but implies it is superior to screenshot-based methods. It relies heavily on the user understanding which specific type of data extraction they need.

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

All Johto Data 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?