Laso Finance

get_agent_wallet

Read-onlyIdempotent

Get your managed agent wallet: whether one exists, its funding addresses on Solana and Base, its USDC balance, and whether it needs funding. Paid tools draw from this wallet, so check it before your first paid call. Fund it by sending USDC on Solana to wallet_address, or USDC on Base to base_wallet_address; both land in the same balance. balance_usdc is the total across the wallet's Solana and Base sides, which every payment and transfer can draw on, split as solana_balance_usdc and base_balance_usdc; base_balance_usdc is null when its live chain read fails. These on-chain balances are separate from the Laso account balance that get_account_balance reports: a paid call shows up there as a deposit followed by a debit, so an account balance of 0 after a purchase is expected. tokens lists every asset the Solana side holds, USDC included (mint, symbol, amount, usd_value; mint is native for SOL); send any of them with agent_wallet_transfer by passing mint, or convert them to USDC with agent_wallet_swap.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 26, 2026

removedInput schema / properties / auth_token

Removed value: -{
-  "description": "Laso credential. Only if the MCP connection has no Authorization header.",
-  "type": "string"
-}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "type": "object"
+}

Changed1 schema field changedSep 26, 2026
- changedOutput schema / (root)
```
Previous value: -{
-  "type": "object"
-}New value: +null
```
First observedSep 26, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare readOnly/idempotent/openWorld=false; the description adds substantial behavioral context the annotations cannot: a documented failure mode ('base_balance_usdc is null when its live chain read fails'), how balances aggregate across chains, and the deposit-then-debit accounting quirk that makes an account balance of 0 after purchase expected.

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 purpose and the pre-call check, then moves to funding, balance semantics, and token list. The long semicolon-chained sentence about balances is dense and could be split, but nearly every clause carries information an agent would otherwise get wrong.

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?

An output schema exists, yet the description still supplies the cross-tool accounting model (wallet balance vs. Laso account balance) and the null-on-chain-read-failure caveat that the schema alone would not make actionable. Nothing needed to call and correctly interpret this tool is missing.

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?

Zero parameters, so the baseline is 4. The description instead spends its budget explaining output fields (balance_usdc, solana_balance_usdc, base_balance_usdc, tokens) with enough semantics that an agent can interpret results without guessing.

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?

Opens with a specific verb+resource ('Get your managed agent wallet') and immediately enumerates what it returns: existence, Solana/Base funding addresses, USDC balance, funding status. It also differentiates itself from siblings by name (get_account_balance, agent_wallet_transfer, agent_wallet_swap).

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?

States explicit when-to-use ('check it before your first paid call' since 'paid tools draw from this wallet') and gives the follow-up routing: send assets via agent_wallet_transfer or convert via agent_wallet_swap. It also preempts a likely confusion by explaining when get_account_balance is the wrong place to look.

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

All Laso Finance tools Inspect

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

Need Help?