Skip to main content
Glama

Archive or restore bank account

crunch_archive_bank_account
Idempotent

Archive a bank account you no longer use so it stays in your records but is hidden, or restore an archived account by setting archive to false.

Instructions

Archive a bank account you no longer use (it stays in your records but is hidden), or restore an archived one with archive=false.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bank_account_id": "<bank_account_id>"
    },
    "name": "crunch_archive_bank_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
archiveNotrue to archive (default), false to restore
dry_runNoPreview: return the request that would be sent (for an update, the fields that would change) without sending it
bank_account_idYesBank account ID (see crunch_list_bank_accounts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, and the parenthetical ('stays in your records but is hidden') usefully confirms it is a soft-hide, not a deletion. Beyond that the description adds little behavior: the dry_run preview mode, documented only in the schema, is not surfaced as part of the narrative.

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?

A single sentence with the archive action front-loaded and the restore path following the semicolon. No wasted words, and the effect of archiving is folded in compactly.

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?

For a simple three-parameter, non-destructive state toggle with full schema coverage and no output schema, the description covers what an agent needs to choose the tool and set the mode. It stops short of mentioning the dry_run escape hatch, which is the one omission worth noting.

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 all three parameters including archive and dry_run carry their own explanations. The description restates the archive=false convention but adds no syntax, defaults or constraints beyond what the schema already supplies; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Archive a bank account') and covers the dual mode by naming the restore path explicitly. It does not compare itself to nearby tools such as crunch_update_bank_account or crunch_archive_credit_card, so an agent gets the purpose but not sibling differentiation from the text alone.

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?

Gives clear selection context: archive when the account is 'no longer use[d]', and pass archive=false to restore. It offers no explicit exclusions or named alternatives, leaving the agent to infer that edits to live account details belong to crunch_update_bank_account.

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

Deploy Server

Other Tools