Skip to main content
Glama
Sign In

WattCoin

by io.github.WattCoin-Org
OverviewDiscussionsAdmin

WattCoin: Web scrape

web_scrape

WattCoin: Fetch a web page and return its content as text. Pick one payment path: the free tier (agent_key, text format only, small daily quota) or pay-per-request in WATT (wallet plus a single-use tx_signature sent within the allowed age; see get_pricing for the price and payment wallet). Not idempotent: each call uses quota or consumes a payment signature. Returns the page content as text.

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

Input Schema

NameRequiredDescriptionDefault
urlYeshttp(s) URL to scrape, e.g. https://example.com/page
formatNoOutput format, default text. The free tier covers text onlytext
walletNoWATT-payment path: Solana wallet address, base58, 32-44 characters (e.g. 7vvNk...). The paying wallet
agent_keyNoFree-tier path: your agent API key, format wck_.... Wallet and tx_signature are not needed with it
tx_signatureNoWATT-payment path: Solana transaction signature of your payment; usable once

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / agent_key / description
      Previous value: -"Free-tier path: your agent API key (wck_...). Wallet and tx_signature are not needed with it."New value: +"Free-tier path: your agent API key, format wck_.... Wallet and tx_signature are not needed with it"
    • addedInput schema / properties / format / default
      Added value: +"text"
    • changedInput schema / properties / format / description
      Previous value: -"text (default), markdown, html. The free tier covers text only."New value: +"Output format, default text. The free tier covers text only"
    • addedInput schema / properties / format / enum
      Added value: +[
+  "text",
+  "markdown",
+  "html"
+]
    • changedInput schema / properties / tx_signature / description
      Previous value: -"WATT-payment path: payment transaction signature"New value: +"WATT-payment path: Solana transaction signature of your payment; usable once"
    • changedInput schema / properties / url / description
      Previous value: -"URL to scrape"New value: +"http(s) URL to scrape, e.g. https://example.com/page"
    • addedInput schema / properties / url / format
      Added value: +"uri"
    • changedInput schema / properties / wallet / description
      Previous value: -"WATT-payment path: your Solana wallet (the payer)"New value: +"WATT-payment path: Solana wallet address, base58, 32-44 characters (e.g. 7vvNk...). The paying wallet"
  2. Changed5 schema fields changed
    • addedInput schema / properties / agent_key
      Added value: +{
+  "description": "Free-tier path: your agent API key (wck_...). Wallet and tx_signature are not needed with it.",
+  "type": "string"
+}
    • changedInput schema / properties / format / description
      Previous value: -"text (default), markdown, html"New value: +"text (default), markdown, html. The free tier covers text only."
    • changedInput schema / properties / tx_signature / description
      Previous value: -"Payment transaction signature"New value: +"WATT-payment path: payment transaction signature"
    • changedInput schema / properties / wallet / description
      Previous value: -"Your Solana wallet (the payer)"New value: +"WATT-payment path: your Solana wallet (the payer)"
    • changedInput schema / required
      Previous value: -[
-  "url",
-  "wallet",
-  "tx_signature"
-]New value: +[
+  "url"
+]
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare idempotentHint=false and openWorldHint=true; the description adds the reason behind them ('each call uses quota or consumes a payment signature'), plus auth requirements (single-use tx_signature within an allowed age) and the free-tier format restriction. It stops short of describing failure modes or what happens when a signature is stale.

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?

Front-loaded with the core action, then payment paths, then the non-idempotency warning. Minor waste: the return value ('content as text') is stated in both the first and last sentence.

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?

With five parameters and no output schema, the description covers the action, the two auth/payment modes, the format constraint, non-idempotency, and the return shape, and refers out to get_pricing for the one variable it cannot inline. 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.

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds semantics the schema does not encode: the wallet + tx_signature pair and agent_key are alternative payment paths, not independent options, and the free tier restricts format to text. That mutual-exclusivity framing materially helps correct invocation.

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 ('Fetch a web page and return its content as text') with unambiguous scope. No sibling tool performs fetching/scraping, so the agent can distinguish it from browse_marketplace and the rest of the marketplace tools without opening a 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?

Explicitly frames the two mutually exclusive invocation paths (free tier via agent_key, text-only with a small daily quota; or WATT pay-per-request via wallet + tx_signature) and points to get_pricing for price and the payment wallet. It does not say when to prefer this tool over browse_marketplace, but the call-mode guidance is concrete.

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

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