Skip to main content
Glama

Set credit card opening balance

crunch_set_credit_card_opening_balance
Idempotent

Sets or updates a credit card's opening balance—the amount owed when you began using Crunch—so the account starts with accurate figures.

Instructions

Set a credit card's opening balance (the amount owed when you started using Crunch for it). Creates it, or updates an existing editable one.

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": {
      "credit_card_id": "<credit_card_id>",
      "opening_balance": "<opening_balance>"
    },
    "name": "crunch_set_credit_card_opening_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoPreview: return the request that would be sent (for an update, the fields that would change) without sending it
credit_card_idYesCredit card ID (see crunch_list_credit_cards)
opening_balanceYesOpening balance, for example 250.00

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the mutation and repeat-safety profile is covered. The description adds genuinely new detail with the upsert behavior and the word 'editable', which hints that some opening balances are locked. It never says what happens when the existing balance is not editable — error, no-op, or silent overwrite — which is the key behavioral unknown left.

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?

Two short sentences, front-loaded with the action and its domain definition, then the upsert behavior. No filler or restatement of the title beyond what the definition of the term requires.

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 three-parameter upsert with full schema coverage and annotations, this is close to sufficient: no output schema means return values need not be explained, and dry_run is covered by the schema. The remaining gap is the outcome when the existing opening balance is not editable, plus any permission or currency assumption.

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%, including the dry_run preview semantics, credit_card_id cross-reference and the opening_balance pattern and example, so the baseline is 3. The description's parenthetical explains what the balance actually represents, a modest conceptual gain over the schema's 'Opening balance, for example 250.00', but adds no syntax or edge-case meaning (currency, sign convention for credits).

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 ('Set a credit card's opening balance') and defines the domain term in parentheses as the amount owed at onboarding. It also discloses the upsert shape ('Creates it, or updates an existing editable one'), which separates it from a plain credit-card update. It does not name a sibling such as crunch_get_opening_balances, so it stops short of full differentiation.

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 rather than prescribed: an agent can infer this is the write path for an opening balance, and the upsert wording removes any create-vs-update choice. There is no explicit when-not-to-use guidance and no pointer to crunch_update_credit_card or crunch_get_opening_balances for adjacent needs.

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