Skip to main content
Glama

t2000_withdraw

Transfer funds from savings to checking accounts. Specify dollar amount or use "all" for full balance, with optional preview mode before executing.

Instructions

Withdraw from savings back to checking. Amount is in dollars. Use "all" to withdraw everything. Set dryRun: true to preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesDollar amount to withdraw, or "all"
dryRunNoPreview without signing (default: false)

Implementation Reference

  • The implementation of the 't2000_withdraw' tool, which handles withdrawals from savings, including a dry-run preview mode and mutex-locked execution.
    server.tool(
      't2000_withdraw',
      'Withdraw from savings back to checking. Amount is in dollars. Use "all" to withdraw everything. Set dryRun: true to preview.',
      {
        amount: z.union([z.number(), z.literal('all')]).describe('Dollar amount to withdraw, or "all"'),
        dryRun: z.boolean().optional().describe('Preview without signing (default: false)'),
      },
      async ({ amount, dryRun }) => {
        try {
          if (dryRun) {
            agent.enforcer.assertNotLocked();
            const positions = await agent.positions();
            const health = await agent.healthFactor();
            const savings = positions.positions
              .filter(p => p.type === 'save')
              .reduce((sum, p) => sum + p.amount, 0);
    
            return {
              content: [{
                type: 'text',
                text: JSON.stringify({
                  preview: true,
                  amount: amount === 'all' ? savings : amount,
                  currentSavings: savings,
                  currentHealthFactor: health.healthFactor,
                }),
              }],
            };
          }
    
          const result = await mutex.run(() => agent.withdraw({ amount }));
          return { content: [{ type: 'text', text: JSON.stringify(result) }] };
        } catch (err) {
          return errorResult(err);
        }
      },
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions the 'dryRun' feature for previewing, which adds some behavioral context, but lacks critical details such as authentication requirements, rate limits, whether the withdrawal is immediate or processed later, potential fees, or error conditions. For a financial transaction tool with zero annotation coverage, this is insufficient.

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 front-loaded with the core purpose in the first sentence, followed by concise details about parameters. Every sentence earns its place with no wasted words, making it highly efficient and easy to parse.

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

Completeness3/5

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

Given the complexity of a financial withdrawal tool with no annotations and no output schema, the description is moderately complete. It covers the basic action and parameter usage but lacks details on behavioral aspects like side effects, return values, or error handling. It's adequate for minimal understanding but has clear gaps for safe and effective use.

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?

Schema description coverage is 100%, so the schema already documents parameters well. The description adds value by clarifying that 'amount' is in dollars and that 'all' withdraws everything, which reinforces the schema but doesn't provide new semantics beyond it. With 2 parameters and high schema coverage, a baseline of 3 is appropriate, but the extra clarification earns a slightly higher score.

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 specific action ('Withdraw from savings back to checking') with the resource ('savings') and destination ('checking'), distinguishing it from siblings like 't2000_save' (deposit) or 't2000_balance' (query). It uses precise verbs and specifies the financial transaction scope.

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 provides clear context for usage with the 'dryRun' parameter to preview without signing, implying it's for testing or verification before actual withdrawal. However, it doesn't explicitly state when to use this tool versus alternatives like 't2000_save' or 't2000_repay', nor does it mention 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/mission69b/t2000'

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