CleanWeb x402 — Smart Web Scraping & YouTube AI Agent

get_vault_balance

Check remaining pre-funded USDC balance, total usage, and session status for an agent wallet or session key. Verify funds before heavy tasks to ensure zero-latency execution.

Instructions

Checks the remaining pre-funded USDC balance, total usage, and session status for an agent wallet address or session key.

Usage Guidelines:

Use this tool before executing heavy tasks to verify sufficient balance for zero-latency execution.
Returns: Agent address, available balance in USDC, total deposited, total consumed, queries handled, and session key.
Do NOT use for querying pricing or chain parameters (use get_payment_info).

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": {
      "agent_address_or_key": "<agent_address_or_key>"
    },
    "name": "get_vault_balance"
  }
}

Input Schema

Name	Required	Description	Default
`agent_address_or_key`	Yes	Ethereum/Polygon address (0x...) or session key (sk_...) to query balance for.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.2.6Sep 11, 2026
- addedInput schema / properties / agent_address_or_key / description
```
Added value: +"Ethereum/Polygon address (0x...) or session key (sk_...) to query balance for."
```
- addedInput schema / properties / agent_address_or_key / examples
```
Added value: +[
+  "0x71C...397",
+  "sk_cleanweb_agent_01"
+]
```
- addedInput schema / properties / agent_address_or_key / pattern
```
Added value: +"^(0x[a-fA-F0-9]{40}|sk_[a-zA-Z0-9_-]+)$"
```
Addedv1.2.5Sep 4, 2026

TDQS

A4.3/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. The verb 'Checks' implies a read-only operation, and the return fields are listed, but it does not explicitly state safety traits (e.g., read-only, non-destructive) or authentication/rate-limit requirements. Partial transparency.

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 front-loaded with purpose, then cleanly organized into usage guidelines and returns. Every sentence adds value, and there is no redundant or filler text.

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 simple read-only balance check with one parameter and an output schema, the description covers purpose, usage guidelines, and return fields. The output schema handles return values, so the description is complete without needing to explain them further.

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 the schema already documents the single parameter thoroughly. The description restates 'for an agent wallet address or session key' but adds no additional syntax, format, or edge-case detail beyond the schema. Baseline 3.

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?

The description states a specific verb (checks) and resource (remaining pre-funded USDC balance, total usage, session status), scoped to an agent wallet address or session key. It distinguishes itself from the sibling get_payment_info by explicitly excluding pricing and chain parameters.

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?

It gives explicit when-to-use guidance ('Use this tool before executing heavy tasks to verify sufficient balance') and when-not-to-use guidance ('Do NOT use for querying pricing or chain parameters (use get_payment_info)'), naming the alternative tool directly.

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

Deploy Server