agentcard

list_cards

Read-onlyIdempotent

The user's wallet: every live card they hold, with IDs, last four digits, expiry, balance, and status. Start here to find available cards; if none are returned, call create_card to issue one. When the shared wallet is enabled, wallet lists every card across all connected apps and companies, each tagged with its source (kind personal/company, the issuing app, and the company where applicable) — cards created by another app or company are read-only from this session: get_card_details and close_card will not work on them.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`cards`	No	The user's own virtual cards.
`count`	No	Total number of cards across the user's own cards and any connected-account cards.
`wallet`	No	One-wallet view (present when the shared wallet is enabled): every LIVE card across personal and company sources, each tagged with its provenance. Closed cards are excluded; transactions carry history.
`message`	Yes	Human-readable list of cards (or an empty-state message).
`connectedAccounts`	No	Read-only cards issued and managed by an organization the user is linked to.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed3 schema fields changedAug 13, 2026

changedOutput schema / properties / wallet / items / properties / source / properties / app / description

Previous value: -"OAuth client id of the app that minted the card (null for first-party surfaces)."New value: +"OAuth client id of the app that created the card (null for first-party surfaces)."

changedOutput schema / properties / wallet / items / properties / source / properties / appName / description

Previous value: -"Display name of the minting app (null when unknown or first-party)."New value: +"Display name of the issuing app (null when unknown or first-party)."

changedOutput schema / properties / wallet / items / properties / source / properties / kind / description

Previous value: -"personal = minted on the user's own account; company = minted under a company the user is connected to."New value: +"personal = created on the user's own account; company = created under a company the user is connected to."

First observedJul 28, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes beyond the readOnlyHint and destructiveHint annotations by detailing the shared wallet mode, cross-app source tagging, and the read-only restriction for cards issued by other apps/companies. This is valuable behavioral context not present in the annotations.

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?

The description is three sentences, each delivering essential information: purpose, first-step usage, and shared wallet behavior. No filler or redundancy; it is well-structured and front-loads the core purpose.

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?

The description covers the main use case, edge cases for shared wallets, and cross-app restrictions. Since an output schema exists and there are no parameters, no additional return value or parameter documentation is needed.

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 has 0 parameters and schema description coverage is 100%, so the description is not required to add parameter details. With no parameters, baseline 4 is appropriate.

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 description clearly states the tool's function: listing the user's live cards with IDs, last four digits, expiry, balance, and status. It also distinguishes from siblings by noting that cards from other apps are read-only and that get_card_details and close_card won't work on them, and points to create_card as a follow-up.

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?

Explicitly instructs to 'Start here to find available cards' and directs to call create_card if no cards are returned. It also explains the shared wallet behavior and clarifies which operations are not supported on read-only cards, providing clear when-to-use and when-not-to-use guidance.

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

All agentcard tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Most tools have clearly distinct purposes, especially in areas like card management and shopping. However, the KYC flow has multiple overlapping tools (start_kyc, get_kyc_status, check_kyc_document, submit_kyc_document, submit_kyc_fields) that could confuse an agent despite detailed descriptions.

Naming Consistency4/5

Tool names consistently use snake_case with a verb_noun pattern (e.g., add_funds, create_card, list_cards). A few exceptions like surprise_me and whoami break the pattern but are still intuitive overall.

Tool Count3/5

50 tools is on the high side for a single server, but the broad domain (cards, shopping, KYC, support, settings) partially justifies it. Some tools could be merged (e.g., KYC flow tools) without losing clarity.

Completeness4/5

The tool surface covers core workflows: CRUD for cards, transactions, KYC, support, shopping, and account management. Minor gaps exist (e.g., no update_card general, no cancel order in shopping), but overall the set is comprehensive for the stated purpose.

Resources

Need Help?