Skip to main content
Glama
Sign In

apibase

by io.github.whiteknightonhorse
OverviewDiscussionsAdmin

Inferrail Web Read

inferrail.web.read_page
Read-onlyIdempotent

Read one public web page as clean Markdown (title, main text, headings, lists, links) with word count, a SHA-256 content hash and the provider receipt. APIbase pays the provider per call over x402; your payment is settled only when the page is delivered. Source: Inferrail Web Read.

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": "inferrail.web.read_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL of the web page to read (e.g. "https://example.com/")

Output Schema

NameRequiredDescriptionDefault
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description then adds genuinely new behavior: APIbase pays the provider per call over x402 and settlement only occurs on delivery, which is critical cost context an agent would not otherwise have. It stops short of error/failure behavior (e.g. what happens when payment fails).

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 core action is front-loaded in the first clause before the payment details, and there is no filler. The parenthetical field list and the payment sentence make the single sentence dense, but each element carries information.

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?

An output schema exists, so the description need not explain return values, yet it still summarizes the payload shape briefly. Given the tool's simplicity and the rich annotations, what remains missing is only edge-case behavior (payment failure, non-HTML content), which is a minor gap.

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 already documented with format, pattern and an example. The description's "public web page" reinforces the same constraint rather than adding new meaning, so the baseline 3 for high-coverage schemas 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?

The description gives a precise verb and resource ("Read one public web page") and enumerates the transformation result ("clean Markdown (title, main text, headings, lists, links)"). The scope word "one" makes it clearly a single-page fetch, which is distinguishable from the search.* siblings that return result sets.

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 rather than stated: "public" and "one" signal the scope limit, and the mention of a per-call paid provider hints at why one might hesitate. But there is no explicit when-to-use versus the search or screenshot siblings, and no stated exclusions (paywalls, auth-required pages, PDFs) beyond the word "public".

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

All apibase toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources