Skip to main content
Glama

Get opening balances

crunch_get_opening_balances
Read-only

Retrieve opening balances for bank accounts or credit cards and check whether each balance can still be edited. Use account IDs and an optional account type to target specific records.

Instructions

Get the opening balances of bank accounts or credit cards, and whether each can still be edited.

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": {
      "account_ids": "<account_ids>"
    },
    "name": "crunch_get_opening_balances"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoAccount type: bank_accounts (default) or credit_cards
account_idsYesBank account or credit card IDs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a genuine behavioral detail the annotations lack: that the response says whether each balance can still be edited. It says nothing about how partial or invalid ID sets are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the action and resource, with no filler. The trailing editability clause is slightly awkward but carries real information.

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?

A small two-parameter read tool with no output schema, so the description's only real burden is explaining the return shape. It hints at the editability flag but does not say what a missing or inaccessible account ID produces, leaving a modest gap.

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 type enum and account_ids array are already documented. The description's 'bank accounts or credit cards' merely echoes the enum values and adds no format or batching detail beyond the schema. 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 (get opening balances) and names the two entity types covered (bank accounts or credit cards), plus the editability flag it returns. An agent can distinguish this from crunch_list_bank_accounts or crunch_get_bank_account, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to call this versus related reads like crunch_get_bank_account or crunch_list_accounting_periods, and no mention of prerequisites such as knowing the IDs already. The only implicit signal is the plural account_ids, hinting at batch use.

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