Skip to main content
Glama

t2000_save

Deposit USDC to earn yield at optimal rates. Specify dollar amount or "all" for entire balance, with dry-run preview option.

Instructions

Deposit USDC to savings at the best USDC rate (earns yield). Amount is in dollars. Use "all" to save entire available balance. Set dryRun: true to preview. This saves USDC as USDC — do NOT suggest swapping to other assets first. If the user later wants to chase higher yields on other assets (e.g. USDe), use t2000_rebalance AFTER saving.

Input Schema

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

Implementation Reference

  • Implementation of the t2000_save tool.
    server.tool(
      't2000_save',
      'Deposit USDC to savings at the best USDC rate (earns yield). Amount is in dollars. Use "all" to save entire available balance. Set dryRun: true to preview. This saves USDC as USDC — do NOT suggest swapping to other assets first. If the user later wants to chase higher yields on other assets (e.g. USDe), use t2000_rebalance AFTER saving.',
      {
        amount: z.union([z.number(), z.literal('all')]).describe('Dollar amount to save, or "all"'),
        dryRun: z.boolean().optional().describe('Preview without signing (default: false)'),
      },
      async ({ amount, dryRun }) => {
        try {
          if (dryRun) {
            agent.enforcer.assertNotLocked();
            const balance = await agent.balance();
            const rates = await agent.rates();
            const saveAmount = amount === 'all' ? balance.available - 1.0 : amount;
    
            return {
              content: [{
                type: 'text',
                text: JSON.stringify({
                  preview: true,
                  amount: saveAmount,
                  currentApy: rates.USDC?.saveApy ?? 0,
                  savingsBalanceAfter: balance.savings + saveAmount,
                }),
              }],
            };
          }
    
          const result = await mutex.run(() => agent.save({ amount }));
          return { content: [{ type: 'text', text: JSON.stringify(result) }] };
        } catch (err) {
          return errorResult(err);
        }
      },
    );
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well by disclosing key behaviors: it's a deposit operation (implies mutation), supports preview mode via dryRun, allows saving entire balance with 'all', and yields earnings. However, it lacks details on permissions, rate limits, or error conditions, which would be helpful for a financial tool.

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, followed by concise usage notes and exclusions. Every sentence earns its place by adding critical information without redundancy, making it efficient and well-structured for an AI agent.

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

Completeness4/5

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

Given no annotations and no output schema, the description does a good job covering purpose, usage, and key behaviors. However, as a financial mutation tool, it could benefit from more details on security implications, return values, or error handling to be fully complete for an agent.

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 the schema already documents both parameters thoroughly. The description adds minimal value beyond the schema by mentioning 'all' and dryRun usage, but doesn't provide additional syntax or format details. This meets the baseline for high schema coverage.

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 ('Deposit USDC to savings'), resource ('USDC'), and goal ('at the best USDC rate (earns yield)'). It distinguishes from siblings by explicitly mentioning t2000_rebalance as an alternative for different use cases, avoiding confusion with tools like t2000_invest or t2000_exchange.

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?

The description provides explicit guidance on when to use this tool ('to save USDC as USDC'), when not to use it ('do NOT suggest swapping to other assets first'), and alternatives ('use t2000_rebalance AFTER saving' for chasing higher yields). It also specifies context like using 'all' for entire balance and dryRun for previews.

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