cuporacle-mcp

Fund the agent wallet (CCTP)

wallet_fund_guide

Read-only

Get a step-by-step CCTP guide to transfer USDC from Base, Arbitrum, or Ethereum to Injective and fund wc_edge payments.

Instructions

Return a CCTP runbook to move USDC from Base/Arbitrum/Ethereum onto Injective so the agent can pay for wc_edge. Routes the real moves to the InjectiveLabs/mcp-server (account_balances, cctp_supported_chains, cctp_attestation_status, cctp_mint). Free, read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wallet_fund_guide"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	No	Source chain that holds your USDC (default: base).

Output Schema

Name	Required	Description	Default
`steps`	Yes
`destination`	Yes
`source_chain`	Yes
`runbook_markdown`	Yes
`usdc_on_injective`	Yes
`source_cctp_domain`	Yes
`injective_mcp_tools`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 17, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations show readOnlyHint=true; description adds that it is free and read-only, and routes to other tools, providing useful context beyond annotations.

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?

Two sentences, no wasted words, well-structured and front-loaded with core purpose.

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?

Given output schema exists, description covers main functionality and routing, but misses prerequisites (e.g., having USDC on source chain).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

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

The description mentions only Base/Arbitrum/Ethereum, while the enum includes five more chains, creating a contradiction that may mislead agents.

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 clearly states the tool returns a CCTP runbook for moving USDC from specific chains to Injective to fund the agent wallet for wc_edge, distinguishing it from sibling tools.

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?

The description indicates use when the agent needs to fund wc_edge, but does not explicitly list when not to use or alternatives, though sibling tools are different.

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

Deploy Server