Skip to main content
Glama
FTHTrading

Genesis402

by FTHTrading
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Fetch one public web page and return it as clean text with i

genesis402_web_extract

Fetch any public web page and extract clean text with title, headings, and links. Get full page content instead of a summary.

Instructions

Paid (price from the live 402 quote). Fetch one public web page and return it as clean text with its title, headings and links. Use when you need a page's content rather than a summary. Pages behind a login or paywall are not accessible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFull http(s) URL of the public page to fetch.
max_charsNoMaximum characters of text to return, 500 to 60,000.
payment_signatureNoOptional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first; nothing is charged without it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.2
    • addedInput schema / properties / max_chars / description
      Added value: +"Maximum characters of text to return, 500 to 60,000."
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first."New value: +"Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first; nothing is charged without it."
    • addedInput schema / properties / url / description
      Added value: +"Full http(s) URL of the public page to fetch."
  2. First observedv0.3.1

TDQS

A4/5.0
Behavior4/5

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

The description discloses the paid nature ('Paid (price from the live 402 quote)') and the access limitation, which are behavioral facts beyond the annotations (readOnlyHint false, openWorldHint true). It does not detail error behavior or rate limits, but the key side effect (charging) and content restrictions are covered.

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?

Two concise sentences pack purpose, usage, and a key limitation with zero waste. The paid aspect and the core action are front-loaded, making it immediately actionable.

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 simple fetch tool, the description covers the purpose, usage, and limitation. It mentions the return content (title, headings, links) but does not elaborate on max_chars behavior or error cases; however, given the schema coverage and simplicity, this is adequate.

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?

The schema descriptions already cover all three parameters (url, max_chars, payment_signature) with 100% coverage, so the description adds little beyond the 'Paid' context. Baseline 3 applies; no additional semantic enrichment is provided.

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 clearly states the action: 'Fetch one public web page and return it as clean text with its title, headings and links.' It differentiates from a summary tool ('rather than a summary') but does not explicitly name sibling tools, so it stops short of a 5.

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?

Provides explicit guidance on when to use ('when you need a page's content rather than a summary') and a clear constraint ('Pages behind a login or paywall are not accessible'). It does not name alternative tools, but the context is sufficient for an agent to decide.

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