Skip to main content
Glama
Sign In

zFinia Intelligence

by com.zfinia.api
OverviewDiscussionsAdmin

Page Markdown

page_markdown

Fetch a reviewed public page and return its readable content as Markdown, with headings and list structure preserved. Script, style and template content is removed, and nav and aside elements plus anything marked role="navigation" are excluded from the text. Returns the licence and creator, because this content is reusable only on those terms. Truncation at any bound is reported, never silent. Pay 6000 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_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesHTTPS 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.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses content removal rules, excluded nav/aside/role=navigation elements, returned licence and creator information, and explicit truncation reporting. It also states the payment requirement precisely, including 6000 atomic USDC on Base via exact x402 and the MCP challenge-handoff behavior.

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 front-loaded with the tool's function and output, then adds the necessary content exclusions, licence/creator return, truncation behavior, and payment handoff. Every sentence contributes operational or behavioral information without wasted prose.

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?

There is no output schema, but the description explains the return content, preserved structure, licence/creator fields, and truncation reporting. Parameter constraints are fully covered by the schema, and the payment flow is described clearly enough for an agent to understand the x402 handoff.

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 single url parameter is fully documented in the schema with permitted origins, robots.txt handling, and redirect refusal. The description reinforces that the page must be a reviewed public page, but does not add URL formatting or selection details beyond what the schema already provides.

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 gives a specific verb and output: fetch a reviewed public page and return readable Markdown with headings and list structure preserved. It clearly distinguishes the tool's content-extraction role from metadata/link/table siblings by emphasizing readable Markdown, though it does not explicitly name alternatives.

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 description: use this when readable page content as Markdown is needed from a reviewed public origin. It does not explicitly state when to choose this over page_metadata, page_links, page_tables, or the evidence-pack tools, so guidance is adequate but incomplete.

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

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