Skip to main content
Glama

update_card

Change details of an existing card by passing only the fields to modify. Updates name, issuer, network, rates, caps, statement day, or exclusions while leaving other values intact.

Instructions

Change details of an existing card. Only the fields you pass are changed.

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": {
      "card": "<card>"
    },
    "name": "update_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardYesCard id, or its name (a unique part is enough)
nameNo
notesNo
issuerNo
networkNo
base_rateNo
block_inrNo
statement_dayNo
unit_value_inrNo
excluded_categoriesNoReplaces the whole exclusion list

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive mutation. The description adds one genuinely useful behavioral fact beyond them: fields omitted from the call are left untouched, so the agent knows this is a merge-style update rather than a replacement. It does not cover permission requirements, failure modes for unknown/ambiguous cards, or what the response contains.

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, the core action first and the update-semantics caveat second. No filler, no restating the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter mutation with 20% schema coverage, two sentences are thin: currency/unit parameters like base_rate and block_inr, the day-of-month constraint, and the replacement behavior of excluded_categories are left entirely unexplained. The presence of an output schema excuses it from documenting return values, but not from the parameter and risk gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20% across 10 parameters, so the description must compensate and largely does not — it never explains name vs notes semantics, rate/INR units, statement_day range, or the destructive list replacement for excluded_categories (that only appears in the schema). Its single partial-update sentence applies to all fields generically rather than to any specific parameter.

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: "Change details of an existing card." The mutating, existing-record scope is unambiguous and naturally distinguishable from add_card/remove_card. No explicit sibling routing, but the purpose itself is clear.

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?

"Only the fields you pass are changed" implies when this tool is appropriate (partial edits rather than removal or creation), but there is no explicit when-not guidance, no mention of what to do on ambiguous card names, and no warning about whole-list replacement for list-type fields.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.