Johto Data

Johto Data Extract JSON-LD

extract_jsonld

Read-only

Extract application/ld+json script blocks from caller-supplied HTML, preserving parsed fields and source offsets. Reports malformed blocks. No URL fetch, JavaScript execution or remote context resolution. Caller must have rights to supplied HTML. Costs $0.0009 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": {
      "html": "<html>"
    },
    "name": "extract_jsonld"
  }
}

Input Schema

Name	Required	Description	Default
`html`	Yes	Caller-supplied HTML, max 60000 characters; no URL fetch

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond readOnlyHint and openWorldHint, the description discloses pricing ($0.0009 USDC per call via x402), the payment handshake and retry mechanism, the preservation of parsed fields and source offsets, malformed block reporting, and the caller's rights requirement. It also reinforces the no-fetch/no-execution behavior. This is rich behavioral context that annotations alone do not provide.

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?

The description is front-loaded with the core action and constraints, then covers exceptions and payment. It is dense but structured. Payment instructions are necessary for correct invocation. A few clauses could be slightly tightened, but overall it is efficient.

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?

For a single-parameter, read-only extraction tool with no output schema, the description covers purpose, input restrictions, malformed-block handling, pricing/payment workflow, and safety exclusions. Nothing needed to invoke the tool correctly appears to be 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 one required parameter ('html') with 100% schema description coverage, including the max 60000 characters and no URL fetch. The description reinforces 'caller-supplied HTML' and 'No URL fetch' but does not add format, encoding, or validation semantics beyond the schema. Baseline 3 is appropriate when the schema already documents the only parameter fully.

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?

The description states a specific verb and resource: 'Extract application/ld+json script blocks from caller-supplied HTML.' It also adds scope details like preserving parsed fields and source offsets. Sibling differentiation is implicit through exclusions (no URL fetch, no JS execution) but no sibling is named 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?

The description clearly delimits usage: only caller-supplied HTML, no URL fetch, no JavaScript execution, no remote context resolution. It does not name alternative tools for those excluded cases, so the agent must infer the alternatives from the sibling list.

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?