Skip to main content
Glama

Set default credit card

crunch_set_default_credit_card
Idempotent

Set a chosen credit card as the default in Crunch accounting by providing its card ID. Use this to ensure future transactions use the intended card.

Instructions

Make a credit card the default 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>"
    },
    "name": "crunch_set_default_credit_card"
  }
}

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)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already establish idempotentHint=true, destructiveHint=false, and readOnlyHint=false, so the safety profile is known. The description adds nothing beyond that — it does not say whether the previously default card is unset, whether an archived card can be promoted, or whether the change is reflected immediately in other resources. With annotations doing all the work, this is a missed opportunity rather than a contradiction.

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 short, front-loaded sentence with no filler, which suits a simple single-purpose tool. The phrasing "the default one" is slightly imprecise, but nothing is wasted.

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?

This is a low-complexity mutation with full schema coverage and no output schema, so most requirements are met. However, the one behavior an agent most needs — what happens to the existing default card and what effect the switch has downstream — is absent, leaving the definition only minimally viable.

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%: credit_card_id is documented with a pointer to crunch_list_credit_cards, and dry_run explains the preview behavior. The description adds no meaning beyond the schema, so the 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?

"Make a credit card the default one" states a specific verb (make default) and resource (credit card), so an agent can identify the operation at a glance and match it to the pattern of the sibling crunch_set_default_bank_account. It loses a point because "default" is never defined — default for what (expenses, payments, exports) is left implicit.

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?

There is no when-to-use guidance, no mention of prerequisites (must the card exist or be unarchived?), and no reference to alternatives such as crunch_update_credit_card or the dry_run preview path. The agent must infer the whole decision context from the name alone.

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