Skip to main content
Glama

Update credit card

crunch_update_credit_card
Idempotent

Update a credit card's details in Crunch, changing only the fields you pass. Use it to edit the card name, number, or personal flag without altering other settings.

Instructions

Change a credit card's details. Only the fields you pass change.

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

Input Schema

NameRequiredDescriptionDefault
extraNoAdditional raw fields for the request body, using Crunch's own field names (advanced). Merged last.
dry_runNoPreview: return the request that would be sent (for an update, the fields that would change) without sending it
personalNoA personal card used for business payments
card_numberNoCard number (Crunch usually only needs the last four digits)
display_nameNoName shown in Crunch, for example Amex Business
credit_card_idYesCredit card ID (see crunch_list_credit_cards)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that – it is a partial/PATCH-style update where omitted fields are preserved – but it says nothing about dry_run previews, permissions, or what happens if card_number is supplied alongside a displayed last-four value.

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?

Two short sentences with no filler, and the statement of what the tool does is front-loaded ahead of the update-semantics qualifier. Every sentence earns its place.

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?

For a six-parameter mutation with a nested free-form "extra" object and a dry_run flag, the description covers only the core mutation semantics. The 100% schema coverage and the annotations fill most of the rest, but the agent gets no description-level signal about the advanced extra-field merge or the preview mode, which are the riskiest parts of this call.

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 coverage is 100%, including a meaningful description of credit_card_id pointing at crunch_list_credit_cards, so the schema carries the parameter burden. The description adds only the cross-cutting partial-update rule, which is useful but not parameter-specific, 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?

The description names a specific verb and resource ("Change a credit card's details") and clarifies the update style with "Only the fields you pass change". It does not, however, distinguish this from siblings such as crunch_set_default_credit_card, crunch_set_credit_card_opening_balance, or crunch_archive_credit_card, which an agent might also consider for card modifications.

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 explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative. The partial-update semantics hint at the appropriate scenario, but the agent must infer that the card must already exist and that specialized setters exist for default/opening-balance fields.

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