Skip to main content
Glama
romudille-bit

AgentPay x402 — Economic-intelligence layer for AI Agents

by romudille-bit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

url_reader

Read-onlyIdempotent

Fetch any web page and convert it to clean, LLM-ready markdown by stripping ads, navigation, and boilerplate, returning only the core article or page content for further processing.

Instructions

Convert any URL to clean, LLM-ready markdown. Strips ads, nav, and boilerplate — returns just the content. No API key needed.

Use when: You need to read the content of a web page or article and get clean, structured text for further processing. Not for: you do not have a URL yet — web_search returns pages with content; the page requires a login or renders only in a browser. Returns: content (markdown), url, length, truncated flag Example response: {"url": "https://example.com", "content": "# Example Domain\n\nThis domain is for use in illustrative examples...", "length": 1256, "truncated": false, "source": "jina_reader"}

Price: free. Read-only live public data; no API key, nothing signed or spent. Fails with an error message on an unknown symbol or an unreachable upstream source.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to fetch and convert to markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.4/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. The description adds value beyond them: no API key, cost is free, boilerplate-stripping behavior, and failure on unreachable upstream. The only blemish is a likely copy-paste artifact ('unknown symbol') that doesn't fit a URL reader.

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?

Well front-loaded with the core action first, then labeled Use when / Not for / Returns blocks. Mostly earns its place, though the 'Price: free' line and the stray 'unknown symbol' phrase add noise to an otherwise tight structure.

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?

No output schema exists, so the description compensates by listing return fields (content, url, length, truncated) and giving a concrete example response. Combined with failure behavior and cost, an agent has everything needed to call it correctly.

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 there is a single required URL parameter already documented in the schema. The description adds no URL format, scheme, or validation detail beyond the schema, so the baseline 3 is appropriate.

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 and resource ('Convert any URL to clean, LLM-ready markdown') with concrete scope, and explicitly differentiates from the sibling web_search in the 'Not for' clause. An agent can distinguish this from web_search without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit 'Use when' and 'Not for' sections, naming the alternative (web_search) and the conditions that select it (no URL yet, login-walled, JS-only rendering). This is textbook when/when-not/alternative guidance.

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

Deploy Server

Other Tools