Get withdrawal statuses
Returns the status of withdrawals for the authenticated user. If withdrawal_id is provided, returns a single withdrawal. If omitted, returns all withdrawals.
| Name | Required | Description | Default |
|---|---|---|---|
| withdrawal_id | No | Get a specific withdrawal by ID. If omitted, returns all withdrawals. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / properties / auth_tokenRemoved value: -{
- "description": "Laso credential. Only if the MCP connection has no Authorization header.",
- "type": "string"
-}Output schema / (root)Previous value: -nullNew value: +{
+ "anyOf": [
+ {
+ "properties": {
+ "withdrawal": {
+ "description": "A withdrawal status record.",
+ "properties": {
+ "address": {
+ "description": "The wallet address the withdrawal is sent to",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "amount": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "asset": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "id": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "network": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "state": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "timestamp": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "timestamp_readable": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "tx_hash": {
+ "description": "On-chain transaction hash, present once the withdrawal is processed",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "tx_url": {
+ "description": "Block explorer URL for the transaction, present when tx_hash exists",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": [
+ "object",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ },
+ {
+ "properties": {
+ "withdrawals": {
+ "items": {
+ "description": "A withdrawal status record.",
+ "properties": {
+ "address": {
+ "description": "The wallet address the withdrawal is sent to",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "amount": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "asset": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "id": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "network": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "state": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "timestamp": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "timestamp_readable": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "tx_hash": {
+ "description": "On-chain transaction hash, present once the withdrawal is processed",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "tx_url": {
+ "description": "Block explorer URL for the transaction, present when tx_hash exists",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "type": [
+ "array",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ }
+ ],
+ "type": "object"
+}Output schema / (root)Previous value: -{
- "anyOf": [
- {
- "properties": {
- "withdrawal": {
- "description": "A withdrawal status record.",
- "properties": {
- "address": {
- "description": "The wallet address the withdrawal is sent to",
- "type": [
- "string",
- "null"
- ]
- },
- "amount": {
- "type": [
- "number",
- "null"
- ]
- },
- "asset": {
- "type": [
- "string",
- "null"
- ]
- },
- "id": {
- "type": [
- "string",
- "null"
- ]
- },
- "network": {
- "type": [
- "string",
- "null"
- ]
- },
- "state": {
- "type": [
- "string",
- "null"
- ]
- },
- "timestamp": {
- "type": [
- "number",
- "null"
- ]
- },
- "timestamp_readable": {
- "type": [
- "string",
- "null"
- ]
- },
- "tx_hash": {
- "description": "On-chain transaction hash, present once the withdrawal is processed",
- "type": [
- "string",
- "null"
- ]
- },
- "tx_url": {
- "description": "Block explorer URL for the transaction, present when tx_hash exists",
- "type": [
- "string",
- "null"
- ]
- }
- },
- "type": [
- "object",
- "null"
- ]
- }
- },
- "type": "object"
- },
- {
- "properties": {
- "withdrawals": {
- "items": {
- "description": "A withdrawal status record.",
- "properties": {
- "address": {
- "description": "The wallet address the withdrawal is sent to",
- "type": [
- "string",
- "null"
- ]
- },
- "amount": {
- "type": [
- "number",
- "null"
- ]
- },
- "asset": {
- "type": [
- "string",
- "null"
- ]
- },
- "id": {
- "type": [
- "string",
- "null"
- ]
- },
- "network": {
- "type": [
- "string",
- "null"
- ]
- },
- "state": {
- "type": [
- "string",
- "null"
- ]
- },
- "timestamp": {
- "type": [
- "number",
- "null"
- ]
- },
- "timestamp_readable": {
- "type": [
- "string",
- "null"
- ]
- },
- "tx_hash": {
- "description": "On-chain transaction hash, present once the withdrawal is processed",
- "type": [
- "string",
- "null"
- ]
- },
- "tx_url": {
- "description": "Block explorer URL for the transaction, present when tx_hash exists",
- "type": [
- "string",
- "null"
- ]
- }
- },
- "type": [
- "object",
- "null"
- ]
- },
- "type": [
- "array",
- "null"
- ]
- }
- },
- "type": "object"
- }
- ],
- "type": "object"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is established. The description adds useful contextual behavior: results are scoped to the authenticated user and the single-vs-all behavior depends on the withdrawal_id parameter. No contradictions with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded, stating the core purpose in the first line and then explaining the conditional behavior in two short sentences. Every sentence earns its place without unnecessary elaboration.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only status lookup with one optional parameter and an output schema, the description covers all essential behavior: scope, conditional branching, and result type. An agent has enough information to select and invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the description's parameter guidance mirrors the schema: omitting withdrawal_id returns all withdrawals, providing it returns a single withdrawal. This adds no new semantic detail beyond the schema, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the operation: getting withdrawal statuses for the authenticated user. It also contrasts the two behavioral modes (single withdrawal when an ID is provided, all withdrawals when omitted), which makes the tool's purpose unambiguous among the many status-related siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context on how to use the optional withdrawal_id parameter and what happens when it is omitted. It does not explicitly name alternative tools, but the resource (withdrawals) and scope (authenticated user) make the intended use clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.