Skip to main content
Glama

Request ephemeral card

request_ephemeral_card
Idempotent

Get a single-use virtual card for an approved intent, capped at the approved amount. Retry safely within the idempotency window to receive the same card after a hung checkout.

Instructions

Get a single-use virtual card for an approved intent, capped at the approved amount. Calling this again for the same intent_id inside the idempotency window returns the same card: safe to retry after a hung checkout.

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": {
      "intent_id": "<intent_id>"
    },
    "name": "request_ephemeral_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
intent_idYesThe intent_id returned by submit_purchase_intent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Goes well beyond the idempotentHint annotation by explaining the actual mechanics: same card returned for the same intent_id inside the idempotency window, amount bounded by the approval, and the card is single-use. It omits card expiry/lifetime and what happens when the intent is missing or not approved, which are the remaining behavioral gaps.

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 tightly written sentences, front-loading what is returned and its constraints before the retry semantics. Every clause carries information; nothing is redundant.

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 no output schema, the description still conveys the essential shape of the result (a single-use virtual card, amount-capped) and the retry contract. It could say slightly more about the returned card's lifetime or the failure mode for a non-approved intent, but nothing critical to correct invocation is missing.

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% and already documents intent_id as coming from submit_purchase_intent. The description adds real meaning on top by tying the parameter to an approved intent and an approved amount cap, which the schema does not state.

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 — 'Get a single-use virtual card' — plus the qualifying conditions ('for an approved intent, capped at the approved amount'). It does not explicitly contrast itself with siblings like send_payment or get_intent_status, so differentiation is left mostly implicit through the 'approved intent' prerequisite.

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?

Clear context for when to use: only after an intent is approved, and the retry-after-hung-checkout case is spelled out with the idempotency window as the deciding condition. It stops short of naming an alternative to use instead when the intent is not approved or when a card is not needed.

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