Skip to main content
Glama

Create credit card

crunch_create_credit_card

Add a credit card to Crunch so business expenses can be paid from it, then set the card's opening balance with the separate opening-balance tool.

Instructions

Add a credit card to Crunch so expenses can be paid from it. Set its opening balance with crunch_set_credit_card_opening_balance.

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": {
      "display_name": "<display_name>"
    },
    "name": "crunch_create_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_nameYesName shown in Crunch, for example Amex Business

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds the downstream consequence that expenses can be paid from the card, but says nothing about duplicate handling, required permissions, or what a successful call yields.

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 sentences, zero filler, with the core action stated first and the follow-up step second. Every clause earns its place.

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?

With full schema coverage, no output schema, and annotations present, the description covers purpose and the natural next step. The main remaining gap is the return value (e.g., whether the new card's identifier comes back so it can be passed to the opening-balance tool), which an agent would need to infer.

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 every parameter including the advanced 'extra' and 'dry_run' already carries its own meaning. The description adds no further detail on display_name versus card_number or the personal flag, 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 opens with a specific verb and resource: "Add a credit card to Crunch," plus the business rationale ("so expenses can be paid from it"). It partially distinguishes itself from siblings by pushing the opening-balance concern to crunch_set_credit_card_opening_balance, though it does not explicitly separate itself from crunch_update_credit_card or crunch_create_bank_account.

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

Usage Guidelines4/5

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

It gives a clear creation context and explicitly routes the opening-balance step to a named sibling, which is real when-to-use guidance. It stops short of exclusion rules, such as what to do if the card already exists or when to prefer creating a bank account instead.

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