Skip to main content
Glama

start_card_issuer_link

Send the account holder a code to link the card issuer

Starts the one-time card issuer link: the card issuer sends a one-time code to the account holder. Then call POST /verify-card-issuer-link with the code they enter.

The account holder, never the agent, receives and enters the code. Send your human to their own inbox (or phone) and have them type the code into your interface. Never try to read the account holder's email or messages yourself, and never ask for their email password or access.

Where the code goes. An account with an email on file always gets the code at that email; email and phone are ignored for it. An account with no email (a wallet-only sign-in) must send exactly one of email or phone (E.164). The response names the destination masked, never in full.

Limits. Codes last 10 minutes. At most 5 codes can be sent per account in any rolling hour (429, with Retry-After). Sending a new code replaces the previous one, which then stops working.

Prerequisite: Laso identity verification (403 kyc_required otherwise, with a kyc_url). If the account is already linked, this answers 200 with status: linked and sends nothing, so calling it twice is safe.

This route is free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_card_issuer_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoOnly for an account with no email on file. The account holder's email.
phoneNoOnly for an account with no email on file, instead of `email`. E.164, e.g. `+15551234567`.

Output Schema

NameRequiredDescriptionDefault
noteNo
statusNoOne of: code_sent, linked.
channelNoOne of: email, phone.
sent_toNoThe destination, masked.
expires_atNoWhen the code stops working, in milliseconds since the epoch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A5/5.0
Behavior5/5

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

Annotations only supply readOnly/idempotent/destructive flags; the description adds substantial non-derivable behavior: 10-minute code TTL, a 5-per-rolling-hour limit with `429` + `Retry-After`, code replacement invalidating the prior code, masked destination in the response, and the `403 kyc_required` path. It also adds a security boundary (the account holder, never the agent, receives and enters the code) that no structured field conveys.

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?

It is long for a two-parameter tool, but front-loaded (purpose, then flow, then security, destinations, limits, prerequisite, cost) with bold headers that make it skimmable. Every block carries operational information an agent must act on; there is no filler or restatement of the schema.

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?

Output schema exists, so return values need no explanation, and the description covers the remaining risk surface: auth/KYC prerequisite, rate limiting, error codes, side effects on prior codes, and the human-in-the-loop requirement. Nothing an agent needs to invoke this correctly is missing.

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

Parameters5/5

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

Schema coverage is already 100%, but the description adds the decision rule the schema cannot express: an account with an email on file always receives the code there and both `email` and `phone` are ignored, while a wallet-only account must supply exactly one of them in E.164. That is genuine conditional semantics beyond the property descriptions.

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?

The opening line states a specific verb and resource ('Send the account holder a code to link the card issuer' / 'Starts the one-time card issuer link') and immediately names the paired sibling endpoint, `POST /verify-card-issuer-link`. An agent can distinguish this from `verify_card_issuer_link` and `get_card_issuer_status` 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 Guidelines5/5

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

It gives explicit sequencing (call this, then call verify with the code the holder enters), a hard prerequisite (Laso identity verification, else `403 kyc_required` with `kyc_url`), and the already-linked case where the tool no-ops with `200 status: linked`. Alternatives and the conditions that select them are spelled out rather than implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources