Skip to main content
Glama

arcanumfleet-mcp-server

ArcanumFleet Clean Web Page & Metadata Extractor

arcanum_web_extract
Read-onlyIdempotent

Use this to fetch any public HTTP/HTTPS URL and extract clean LLM-ready text, page title, and meta description without HTML boilerplate — 0 API keys. Costs 0.001 USDC via x402.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic https:// or http:// URL to extract

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world reads, so the safety profile is covered. The description adds genuinely non-derivable behavior: no API keys required and a 0.001 USDC x402 charge, which an agent must know before invoking. It stops short of describing failure modes or the shape/length of the returned text.

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?

One sentence, front-loaded with the action and scope, then the output payload, then the two operational facts (no keys, paid). Every clause carries distinct information with no filler.

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?

With one required param, no output schema, and full annotation coverage, the description covers action, outputs, auth, and pricing — enough to invoke correctly. A note on payment failure handling or content truncation would close the remaining 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 coverage is 100% and the single `url` parameter is fully documented there, so the schema does the heavy lifting. The description only echoes the constraint that the URL must be public HTTP/HTTPS, adding little beyond the schema field text.

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-plus-resource ('fetch any public HTTP/HTTPS URL and extract clean LLM-ready text, page title, and meta description') and names the exact outputs, which no sibling tool provides — the siblings are audits, market data, and wallet tools. An agent can select this without opening the schema.

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?

'Use this to fetch any public HTTP/HTTPS URL' gives a clear triggering context and implies the scope limit (public URLs only). It does not name when not to use it or what to do about paywalled/blocked pages, so it falls short of explicit alternatives or exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.