Skip to main content
Glama
Sign In

gofetch

by dev.getgofetch
OverviewDiscussionsAdmin

Extract JSON fields from a public page ($0.005, only on success)

gofetch_extract
Read-only

Reads static HTML only: it does not run JavaScript, so JS-rendered sites (most big retailers) and bot-protected sites fail with ok:false, error needs_js or blocked, and no charge. Paid: $0.005 USDC on Base via x402, charged only when ok is true. Always returns a fixed envelope ({url, title, markdown, fetched_at, charged}). Optional schema (up to 20 properties) adds data and field_sources. Without an x402 payment in _meta["x402/payment"] it returns the price and how to pay instead.

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": "gofetch_extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) page URL
schemaNoOptional JSON Schema of extra fields to return (max 20 properties)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / schema / description
      Previous value: -"JSON Schema of the fields to return (max 20 properties)"New value: +"Optional JSON Schema of extra fields to return (max 20 properties)"
    • changedInput schema / required
      Previous value: -[
-  "url",
-  "schema"
-]New value: +[
+  "url"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses critical behavior: no JavaScript execution, specific failure modes, no charge on failure, $0.005 USDC on Base via x402 charged only when ok is true, the fixed return envelope, and the unpaid response. These are exactly the operational traits an agent needs before invoking the tool.

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 dense but appropriately sized, with the static-only constraint and charge behavior front-loaded. Every sentence adds information about scope, failure behavior, payment, or return shape.

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?

For a paid, open-world extraction tool with no output schema, the description covers the key operational details: supported content type, failure modes, billing conditions, payment handshake, and return envelope. An agent has enough context to decide whether and how to call it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the input schema already documents both parameters. The description still adds useful meaning by explaining that the optional schema adds data and field_sources, and it reveals the hidden x402 payment requirement in _meta["x402/payment"].

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 clear action and scope: it reads static HTML only, optionally extracts extra JSON fields via a schema, and returns a fixed envelope. It does not explicitly differentiate itself from the gofetch_pricing sibling, but the static-HTML extraction purpose is otherwise specific and understandable.

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 when-not guidance: JS-rendered and bot-protected sites fail with ok:false, needs_js, or blocked. It also explains the payment prerequisite and no-charge-on-failure behavior, though it does not explicitly name alternative tools for JS-rendered pages.

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

All gofetch 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