Skip to main content
Glama

get_card_issuer_status

Read-onlyIdempotent

Check the card issuer link

Reports whether this account has linked the card issuer, the one-time setup every reloadable card route needs first. Until it is linked, those routes answer 400 with No card issuer account is linked to this wallet.

status is one of not_started, code_sent, linked, or kyc_required. Linking is held to Laso identity verification, so an account that has not linked and is not verified reads kyc_required, with a kyc_url to hand the account holder.

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.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
noteNoWhat to do next.
statusNo`not_started`: no link in progress. `code_sent`: a code is waiting for the account holder. `linked`: done. `kyc_required`: the account must complete Laso identity verification first. One of: not_started, code_sent, linked, kyc_required.
channelNo`code_sent` only. Where the code went. One of: email, phone.
kyc_urlNo`kyc_required` only. A one-time identity-verification link to hand the account holder.
sent_toNo`code_sent` only. The destination, masked (e.g. `j***@e***.com`). The full address is never returned.
linked_atNo`linked` only. When the link was made, in milliseconds since the epoch.
expires_atNo`code_sent` only. When the code stops working, in milliseconds since the epoch. Codes last 10 minutes.
attempts_leftNo`code_sent` only. Incorrect entries still allowed before this code is discarded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the `400` error text emitted by dependent routes, the meaning of each status value, the kyc_required fallback condition with its kyc_url, and the unusual constraint that only the account holder may receive and enter the code. It also flags that the route is free.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the one-line purpose and the status enum before the caveats, and nearly every sentence carries operational weight. The bolded account-holder code-handling rule is more relevant to the start/verify steps than to this read-only check, which is a small amount of off-target bulk.

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 not be detailed; the description nonetheless explains the status enum and the kyc_url handoff. Combined with the annotation safety profile, an agent has everything needed to call this zero-argument check correctly and act on its result.

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?

The tool takes zero parameters, so the baseline is 4. There is nothing parameter-level for the description to clarify, and it correctly spends no space on parameter syntax.

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: it reports whether the account has linked the card issuer, and enumerates the exact `status` values returned. This is clearly distinguishable from the mutating siblings start_card_issuer_link and verify_card_issuer_link, which advance the same flow.

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?

Explains the context in which the check matters — it is the one-time setup prerequisite for reloadable card routes, which otherwise answer `400`. It stops short of explicitly naming when to call this versus start_card_issuer_link or verify_card_issuer_link, so the routing is inferred rather than stated.

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