Skip to main content
Glama
Sign In

utility

by xyz.mortal01
OverviewDiscussionsAdmin

extract_url

Fetch a public URL and return clean readable text, title and links. Costs $0.005 USDC (x402, Base). Pass payment in X-PAYMENT header on the /mcp request, or call GET https://mortal01.xyz/extract?url= with an x402 client.

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

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description discloses the $0.005 USDC cost, the X-PAYMENT header requirement, and an alternative GET endpoint. It still omits error behavior, rate limits, and detailed output structure.

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 purpose is front-loaded in the first sentence, and the payment and endpoint details are necessary for invocations. Three sentences with little waste, though the payment instruction is dense.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter extraction tool without an output schema, it covers the key cost/payment flow and names the returned fields. It stops short of error or limit behavior, so it is adequate rather than complete.

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 only parameter is url, and the schema has 0% description coverage. The description adds that it must be a public URL and shows an example query string, but does not specify URL format or edge-case requirements.

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?

It states a specific action: fetch a public URL and return clean readable text, title, and links. That is a clear verb and resource, though it does not explicitly differentiate itself from sibling summarize_url.

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

Usage Guidelines2/5

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

It explains payment and invocation mechanics but gives no guidance on when to choose extract_url versus summarize_url or text_to_json. The only usage constraint stated is that the URL must be public.

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

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