Skip to main content
Glama

Set default bank account

crunch_set_default_bank_account
Idempotent

Set a bank account as the default for new invoices and payments by providing its bank account ID. Use dry run to preview the change before applying it.

Instructions

Make a bank account the default one, used for new invoices and payments.

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_set_default_bank_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.6/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive, closed-world mutation, so the safety profile is covered. The description adds useful context that the default drives new invoices and payments, but does not say whether the previous default is replaced, whether existing documents are affected, or what happens on failure.

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 short sentence with the action front-loaded and the consequence of 'default' appended. No filler or redundancy.

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 two-parameter, non-destructive, idempotent mutation with full schema coverage and rich annotations, the description covers what the tool does and why it matters. Only minor gaps remain, such as replacement behavior for the prior default.

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 both bank_account_id and dry_run are already documented in the schema, including the dry_run preview semantics. The description adds no parameter-level meaning beyond that, so the baseline of 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 ('Make ... the default') and resource ('a bank account'), and clarifies the effect of 'default' as being used for new invoices and payments. It is clearly distinguishable from the credit-card sibling by resource, though it does not name any alternative explicitly.

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?

Usage is implied by the purpose: call it when you want a different account to be the default. There is no explicit when-to-use/when-not guidance, no mention of prerequisites (e.g. the account must exist and be active), and no pointer to crunch_list_bank_accounts for discovering the ID, which the schema does mention.

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