scdo-agent-plugins
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| register_agentB | Create (or reuse) a local SCDO agent identity as a bookkeeping node and start signed heartbeats to the Agent Ledger. The key is created and kept in the local data dir. |
| create_walletA | Create or reuse the agent's x402 wallet and bind it on the Agent Ledger. Fund it with USDC on Base; no ETH is needed. maxUsdc: per-payment limit 0.001 to 1 (default 0.10). dailyUsdc: up to 20 (default 1.00). |
| get_balanceC | On-chain USDC balance of the agent wallet plus the Agent Ledger balances (USDC, test USDC, SCDO). |
| pay_x402A | Pay an HTTP 402 (x402) resource from the agent wallet with an EIP-3009 authorization. The facilitator pays gas. The price is previewed first and must be within maxUsdc and the caps. |
| book_incomeB | Book a settled x402 payment the agent received as income on the Agent Ledger. The ledger checks the signature, the payee wallet and the on-chain receipt. Booking twice is safe (duplicate). agent: 0x agent address if not a local bot. |
| chain_block_heightA | Current block height of the SCDO chain per shard (0 = EVM Shard0, chainId 5680; 1-4 = SCDO Classic). Omit shard for all five. |
| chain_address_balanceA | Native SCDO balance of an address on one shard. Shard0 takes 0x addresses; shards 1-4 take 1S.. classic addresses. |
| chain_tx_statusA | Look up a transaction by hash: success, failed, pending or not_found, with block and amounts when known. |
| chain_address_txsB | Shard0 transaction history of a 0x address from the scdo.com.au explorer API (25 per page). |
| ledger_statsA | Agent Ledger totals: registered agents, online now, count per platform, and service health. |
| ledger_list_agentsB | List agents on the SCDO Agent Ledger (address, online, platform, version, status code). Filter by platform or operator address. |
| ledger_get_agentA | One agent's Agent Ledger record (status, problems, wallets) and, optionally, its book (WSCDO, USDC, test USDC balances and entries). |
| ledger_registrationB | ERC-8004 registration documents of the Agent Ledger and of the main SCDO agent (services, endpoints). |
| games_catalogB | SCDO Games list with play links on scdo.com.au (free demo and SCDO points bookkeeping games). |
| stakewheel_demo_commitA | Get a fresh provably-fair commit (commit_id and server seed hash) for the free Stake Wheel demo. |
| x402_catalogB | Catalog of SCDO x402 pay-to wallets and their pay URLs: base = USDC on Base, scdo = native SCDO on Shard0. |
| x402_quoteA | Fetch the HTTP 402 payment requirements of an x402 URL (price, asset, network, payTo) without paying. |
| x402_relay_statusA | Health and supported schemes of the SCDO x402 Base settlement relay (scdo.com.au/x402-base/). |
| wallet_downloadsA | Latest SCDO Wallet downloads (Windows, Mac) and the Linux scdo-agent, with version, URL and SHA-256. |
| invite_infoB | Invite programme status (contract, limits, live) and, given a Shard0 address, that address's invite link. |
| connect_startA | Start an SCDO Wallet Connect flow for a game: returns a token, nonce and the connect URL to open with SCDO Wallet. returnUrl must be an scdo.com.au /games/ or /play/ URL. No keys are involved. |
| connect_exchangeA | Redeem the one-time return code from SCDO Wallet (valid 300 s, single use) for a browser session and the wallet address. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 22 tools
Most tools target distinct resource/action pairs, and domain prefixes (chain_, ledger_, x402_) help separate them. Some overlap exists among balance-oriented tools (get_balance, chain_address_balance, ledger_get_agent), but descriptions clarify their scopes.
All names use lowercase snake_case with clear domain prefixes, which makes the set readable and predictable. The main deviation is action placement: some are verb_noun (get_balance, create_wallet) while others are resource-first (chain_block_height, ledger_list_agents).
With 22 tools, the server is in the heavy range for a single MCP surface. The tools span wallet, payments, chain, ledger, games, and wallet connect, so the count is somewhat justified, but it still feels broad and borderline excessive.
The set covers many important workflows, including registration, wallet creation, payments, ledger queries, chain lookups, and wallet connect. However, notable lifecycle operations are missing: no direct SCDO/USDC transfer or withdrawal, no ledger agent update/deregister, no full game actions beyond a demo commit, and no invite redemption.