Skip to main content
Glama

Archive or restore credit card

crunch_archive_credit_card
Idempotent

Archive a credit card you no longer use, or restore an archived card by setting archive=false.

Instructions

Archive a credit card you no longer use, or restore an archived one with archive=false.

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

Input Schema

NameRequiredDescriptionDefault
archiveNotrue to archive (default), false to restore
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

A3.6/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, and the description's restore clause usefully confirms the action is reversible rather than a deletion. It says nothing about side effects beyond the flag — whether an archived card disappears from lists, is excluded from balances, or what happens to existing expenses.

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 sentence that leads with the primary action and folds the inverse into a subordinate clause. Nothing is wasted and the key operation is front-loaded.

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 three-parameter toggle with full schema coverage and no output schema, the description covers both modes adequately. The remaining gap is downstream effect disclosure — what archiving does to the card's visibility in reports and lists — which an agent would otherwise have to discover.

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 all three parameters (archive, dry_run, credit_card_id) are already documented in the schema. The description's 'archive=false' restates what the schema says and adds no extra meaning such as a default or a state precondition.

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?

Names a specific verb+resource ('Archive a credit card') and covers the inverse operation ('restore an archived one'), which distinguishes it from crunch_update_credit_card and crunch_get_credit_card. It does not explicitly name a sibling or state how it differs from the bank-account archive tool, 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?

The phrase 'a credit card you no longer use' gives an implied when-to-use and the restore path is spelled out. There is no when-not guidance (e.g., cards tied to open transactions), no prerequisite/permission notes, and no mention of when to prefer dry_run.

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