zFinia Intelligence

Page Metadata

page_metadata

Fetch a reviewed public page and return its title, every meta and Open Graph tag, and the canonical URL. No JavaScript is executed and no script content is read. Returns the licence and creator for the content alongside it, so reuse terms travel with the result. Pay 4000 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_metadata"
  }
}

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

A3.9/5.0

Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and discloses important traits: no JS execution, no script reading, payment cost/network/protocol, challenge handoff rather than direct payment, and licence/creator returned for reuse terms. It does not cover rate limits, error behavior, or idempotency.

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 return values, then follows with safety constraints and payment details. It is efficient, though the licence sentence is slightly verbose.

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 one-parameter tool with no output schema, the description enumerates the main return values and discloses key constraints and payment flow. It is nearly complete, with minor gaps around error handling and the challenge response format.

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 coverage is 100% and the single parameter is fully documented with permitted origins, robots.txt honoring, and redirect refusal. The description adds little parameter-level meaning beyond what the schema already provides, so baseline 3 is appropriate.

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: fetch a reviewed public page and return title, meta/Open Graph tags, canonical URL, licence, and creator. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as page_fingerprint or page_markdown.

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?

It gives clear context: only reviewed public pages, no JavaScript execution, no script content read, and payment via exact x402 with a challenge handoff. It does not name alternative tools or state when another sibling would be preferred.

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?