zFinia Intelligence

Page JSON-LD

page_json_ld

Fetch a reviewed public page and return every JSON-LD structured-data block it declares, parsed. No script is executed. A block that is malformed is reported as a named warning rather than being silently dropped, so a caller can tell an empty page from a broken one. Pay 5000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	HTTPS URL on a reviewed public origin. Permitted origins: https://docs.python.org, https://developer.mozilla.org, https://en.wikipedia.org, https://www.cisa.gov, https://www.sec.gov, https://home.treasury.gov, https://books.toscrape.com. robots.txt is honoured and redirects are refused.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the burden well: it discloses that no script is executed, that malformed blocks surface as named warnings rather than being dropped (empty vs broken distinguishability), and it spells out the x402 payment requirement and challenge handoff. It stops short of describing rate limits, behavior on non-permitted origins, or the concrete shape of the warning objects.

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?

Four sentences, each load-bearing: purpose and parse semantics first, the malformed-block behavior second, the payment handoff last. Nothing is repeated and the most decision-relevant facts are front-loaded.

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?

With no output schema, the description does explain return semantics (all JSON-LD blocks plus named warnings) and the payment flow, which is what an agent most needs. It is slightly incomplete on the exact response envelope and on what happens for out-of-allowlist URLs, though the schema covers the latter partially.

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%, and the url property already documents the allowered origins list, robots.txt honoring, redirect refusal, and maxLength. The description adds no parameter-level meaning beyond that, so the baseline 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?

States a specific verb (fetch) and resource (JSON-LD structured-data blocks) with clear scope: 'every JSON-LD structured-data block it declares, parsed.' This cleanly separates it from siblings like page_metadata, page_markdown, page_tables, and page_links, which each return different page extractions.

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?

Usage is implied by the returned artifact (structured data), but there is no explicit when-to-use guidance and no mention of the sibling extractors an agent should pick instead when it wants markdown, links, tables, or metadata. An agent must infer the routing from the resource noun alone.

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

All zFinia Intelligence 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?