Skip to main content
Glama
nohosa001-pixel

CleanWeb x402 — Smart Web Scraping & YouTube AI Agent

by nohosa001-pixel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_payment_info

Discover Web3 x402 micropayment settings: supported USDC contract addresses, chain IDs, recipient wallet, and pricing tiers before making paid CleanWeb agent queries.

Instructions

Returns complete Web3 x402 micropayment configuration, supported multi-chain USDC contract addresses, EVM network chain IDs (Polygon: 137, Base: 8453, Arbitrum: 42161), recipient wallet address, and pricing tiers for all CleanWeb Studio agent tools.

Usage Guidelines:

  • Use this tool to discover network parameters and deposit requirements before making x402 paid queries.

  • Returns: Structured pricing markdown table, contract addresses, and pre-funded vault endpoints.

  • Do NOT use for checking individual wallet balances (use get_vault_balance).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tierNoOptional specific pricing tier to inspect.
chainNoOptional specific chain name (polygon, base, arbitrum, solana).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.9
    • changedInput schema / properties / chain / description
      Previous value: -"Optional specific chain name (polygon, base, arbitrum)."New value: +"Optional specific chain name (polygon, base, arbitrum, solana)."
  2. Changed2 schema fields changedv1.2.8
    • addedInput schema / properties / chain
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional specific chain name (polygon, base, arbitrum).",
+  "title": "Chain"
+}
    • addedInput schema / properties / tier
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional specific pricing tier to inspect.",
+  "title": "Tier"
+}
  3. First observedv1.2.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations exist, so the description carries the full behavioral burden. It discloses the return shape (pricing markdown table, contract addresses, pre-funded vault endpoints), which is meaningful context, but does not explicitly state read-only nature, auth/API-key needs, or rate limits.

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 purpose, then a clean Usage Guidelines block. The enumerated chain IDs are slightly verbose but carry information not present in the schema (the schema's chain param has no enum), so they earn their place.

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?

An output schema exists, so return-value detail is not strictly required, yet the description summarizes returns anyway. Combined with the explicit exclusion and use-before-paid-query guidance, an agent has enough to call it correctly; only auth/rate-limit context is absent.

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 description coverage is 100%, so both optional params (tier, chain) are already documented in the schema; baseline 3 applies. The description corroborates by listing chains (polygon, base, arbitrum, solana) and pricing tiers, but adds no syntax or format guidance beyond the schema.

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: returns x402 micropayment configuration, USDC contract addresses, chain IDs, recipient wallet, and pricing tiers. It names exactly what the tool surfaces and, via the exclusion line, distinguishes itself from get_vault_balance, so an agent can tell them apart without opening schemas.

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

Usage Guidelines5/5

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

Explicitly says when to use it ('discover network parameters and deposit requirements before making x402 paid queries'), what it returns, and when NOT to use it, naming the alternative (get_vault_balance) for balance checks. Both the positive and negative conditions are stated.

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