Skip to main content
Glama

t2000_config

Configure transaction safeguards for AI agent banking by viewing or setting per-transaction and daily spending limits in dollars.

Instructions

View or set agent safeguard limits (per-transaction max, daily send limit). Use action "show" to view current limits, "set" to update. Values are in dollars. Set to 0 for unlimited.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes"show" to view current limits, "set" to update a limit
keyNoSetting to update: "maxPerTx" or "maxDailySend"
valueNoNew value in dollars (0 = unlimited)

Implementation Reference

  • Handler logic for the t2000_config tool, which handles both 'show' and 'set' actions to view or update safeguard limits.
    async ({ action, key, value }) => {
      try {
        if (action === 'show') {
          const config = agent.enforcer.getConfig();
          return {
            content: [{
              type: 'text',
              text: JSON.stringify({
                locked: config.locked,
                maxPerTx: config.maxPerTx,
                maxDailySend: config.maxDailySend,
                dailyUsed: config.dailyUsed,
              }),
            }],
          };
        }
    
        if (!key || value === undefined) {
          return errorResult(new Error('Both "key" and "value" are required for action "set"'));
        }
    
        if (key === 'locked') {
          return errorResult(new Error('Cannot set "locked" via config. Use t2000_lock to freeze operations.'));
        }
    
        if (key !== 'maxPerTx' && key !== 'maxDailySend') {
          return errorResult(new Error(`Unknown key "${key}". Valid keys: "maxPerTx", "maxDailySend"`));
        }
    
        if (value < 0) {
          return errorResult(new Error('Value must be a non-negative number'));
        }
    
        agent.enforcer.set(key, value);
        return {
          content: [{
            type: 'text',
            text: JSON.stringify({ updated: true, key, value }),
          }],
        };
      } catch (err) {
        return errorResult(err);
      }
    },
  • Zod schema definition for input arguments of t2000_config.
    {
      action: z.enum(['show', 'set']).describe('"show" to view current limits, "set" to update a limit'),
      key: z.string().optional().describe('Setting to update: "maxPerTx" or "maxDailySend"'),
      value: z.number().optional().describe('New value in dollars (0 = unlimited)'),
    },
  • Registration of the t2000_config tool within the MCP server.
    server.tool(
      't2000_config',
      'View or set agent safeguard limits (per-transaction max, daily send limit). Use action "show" to view current limits, "set" to update. Values are in dollars. Set to 0 for unlimited.',
Behavior3/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 discloses that the tool can both read ('view') and write ('set'), which is useful behavioral context. However, it doesn't mention permission requirements, rate limits, or what happens when limits are set (e.g., immediate enforcement). The description adds some value but lacks comprehensive behavioral details.

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 extremely concise and well-structured in two sentences. The first sentence states the purpose, the second provides usage guidelines and key details. Every word earns its place with no redundancy or fluff.

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 the tool's moderate complexity (configuring financial limits) and lack of annotations or output schema, the description is reasonably complete. It covers purpose, usage, and key semantics (dollar values, unlimited=0). However, it doesn't explain return values or error conditions, which would be helpful since there's no output schema.

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 all parameters thoroughly. The description adds minimal value beyond the schema: it reiterates that 'show' views and 'set' updates, and notes 'Values are in dollars. Set to 0 for unlimited.' This provides slight context but doesn't significantly enhance understanding beyond what the schema provides.

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 tool's purpose: 'View or set agent safeguard limits (per-transaction max, daily send limit).' It specifies both the verb ('view or set') and the resource ('agent safeguard limits'), and distinguishes itself from sibling tools by focusing on configuration rather than operations like sending, investing, or checking balances.

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: 'Use action "show" to view current limits, "set" to update.' It clearly differentiates between the two modes of operation, helping the agent choose the correct action based on whether they need to retrieve or modify settings.

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