Skip to main content
Glama

withdraw_compound

Withdraw supplied assets from Compound V3 Comet USDC market. Specify token address and amount, or use 'max' for full withdrawal.

Instructions

Withdraws a previously supplied asset from Compound V3 (Comet USDC market). Pass "max" as the amount to withdraw your entire balance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetYesERC-20 token address to withdraw.
amountYesAmount to withdraw. Use "max" to withdraw entire balance.
chain_idNoChain ID. Default: 1 (Ethereum mainnet).
Behavior2/5

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

No annotations are provided, so the description carries full burden. It discloses the basic action and the max feature, but lacks details on side effects (e.g., gas costs, reverts if insufficient balance), required prior state (must have supplied), or any confirmation step.

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 a single sentence that conveys the action and a key usage point without unnecessary words. It is appropriately front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a DeFi withdrawal tool with no output schema, the description is too brief. Missing context about gas requirements, transaction finality, error conditions, or relationship to supply_compound sibling.

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 baseline is 3. The description adds value for the 'amount' parameter by mentioning 'max', but does not enhance understanding of 'asset' or 'chain_id' beyond the schema.

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 verb 'Withdraws', the resource 'previously supplied asset', and the specific protocol 'Compound V3 (Comet USDC market)'. This distinguishes it from siblings like withdraw_aave and withdraw_erc4626.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a usage hint for the 'amount' parameter ('Pass "max" to withdraw entire balance'), but does not specify when to use this tool versus alternatives, nor any prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/felippeyann/agentfi'

If you have feedback or need assistance with the MCP directory API, please join our Discord server