Skip to main content
Glama

remove_card

Destructive

Preview and delete a credit card with its earn rates, purchases, and point adjustments; requires confirmation to proceed.

Instructions

Delete a card and all its earn rates, purchases and point adjustments. Call once without confirm to see what would be deleted, then ask the user.

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": "remove_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardYesCard id, or its name (a unique part is enough)
confirmNoMust be true to actually delete

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so safety is known from structured data. The description adds the higher-value detail annotations cannot carry: precisely which dependent data is destroyed (earn rates, purchases, point adjustments) and the required dry-run-then-ask sequence. It stops short of stating irreversibility or permission requirements, so not a 5.

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, no filler. The destructive scope is front-loaded and the safe-workflow instruction follows immediately, which is the right order for an agent that may act on the first sentence alone.

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

Completeness5/5

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

An output schema exists so return values need no explanation, and both parameters are fully documented in-schema. For a destructive two-param cascade delete, the description covers scope, gating and user-confirmation duties, leaving nothing an agent needs before calling.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds workflow semantics the schema does not: confirm gates a real delete and the first unconfirmed call is a preview. It also implicitly supports the schema's note that card accepts a name or a unique partial name, though it does not restate the matching rules.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Delete a card") plus the exact cascade scope: earn rates, purchases and point adjustments. That cascade detail is what separates it from remove_earn_rate and delete_purchase, which an agent can tell apart without opening any schema.

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?

Gives an explicit two-step operating procedure: call once without confirm to preview, then ask the user before confirming. It does not name sibling alternatives for removing related sub-resources, but the when-to-use context for this tool itself is unambiguous.

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