Skip to main content
Glama

set_my_cards

Save which supported cards the user holds and optional renewal dates, replacing the current list so payment and credit decisions use the correct cards.

Instructions

Save which cards the user holds (replaces the list), and optionally each card's renewal date. Call it when the user tells you their cards. Only cards from list_cards are supported.

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": {
      "cards": "<cards>"
    },
    "name": "set_my_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardsYesEvery card slug the user holds.
anniversariesNoCard slug → renewal date as MM-DD, when the user knows it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does disclose the critical trait: the write replaces the existing card list rather than merging. It also flags the validation boundary (only list_cards slugs). It does not say whether anniversaries merge or are wiped, nor how invalid slugs are reported, leaving some mutation behavior unspecified.

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, front-loaded with the action and its replace semantics, followed by the trigger and the input constraint. No redundant or filler wording.

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 two-parameter write tool with a fully covered schema and no output schema, the definition covers action, trigger, overwrite behavior, and valid input source. Only the treatment of anniversaries on overwrite is left unstated.

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 both parameters are already documented in structured form, and the description adds little beyond restating that cards is the held-card set and anniversaries is optional. Baseline 3 applies when the schema does the heavy lifting.

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 ('Save which cards the user holds') and immediately qualifies scope with '(replaces the list)' plus the optional renewal-date field. An agent can distinguish this from list_cards and the other siblings without opening the 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?

'Call it when the user tells you their cards' gives a concrete triggering condition, and 'Only cards from list_cards are supported' constrains inputs to a known source. No explicit when-not or pointer to a sibling for related writes (e.g. set_balance), so it stops short of full routing guidance.

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