agentcard

list_cards

Read-onlyIdempotent

The user's wallet: every live card they hold, with IDs, last four digits, expiry, balance, and status, plus vaultCards: the user's OWN cards stored in their Agentcard vault (display fields only; a vaulted card pays through buy with an approval on the user's device (their passkey or master password) and never exposes a number). Start here to find available cards; if none are returned, call create_card. 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).
`vaultCards`	No	The user's own cards stored in their Agentcard vault. Display fields only; they pay through buy with an approval on the user's device (their passkey or master password) and never expose a card number.
`connectedAccounts`	No	Read-only cards issued and managed by an organization the user is linked to.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 16, 2026

changedOutput schema / properties / vaultCards / description

Previous value: -"The user's own cards stored in their Agentcard vault. Display fields only; they pay through buy with a Face ID approval and never expose a card number."New value: +"The user's own cards stored in their Agentcard vault. Display fields only; they pay through buy with an approval on the user's device (their passkey or master password) and never expose a card number."

Changed3 schema fields changedSep 9, 2026

addedOutput schema / properties / cards / items / properties / preset

Added value: +{
+  "description": "Preset summary when the card has restrictions; omit or null when unrestricted.",
+  "properties": {
+    "id": {
+      "type": "string"
+    },
+    "name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "summary": {
+      "type": "string"
+    },
+    "version": {
+      "type": "number"
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}

addedOutput schema / properties / connectedAccounts / items / properties / cards / items / properties / preset

Added value: +{
+  "description": "Preset summary when present.",
+  "properties": {
+    "id": {
+      "type": "string"
+    },
+    "name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "summary": {
+      "type": "string"
+    },
+    "version": {
+      "type": "number"
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}

addedOutput schema / properties / wallet / items / properties / preset

Added value: +{
+  "description": "Preset summary when present.",
+  "properties": {
+    "id": {
+      "type": "string"
+    },
+    "name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "summary": {
+      "type": "string"
+    },
+    "version": {
+      "type": "number"
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}

Changed1 schema field changedSep 7, 2026

addedOutput schema / properties / vaultCards

Added value: +{
+  "description": "The user's own cards stored in their Agentcard vault. Display fields only; they pay through buy with a Face ID approval and never expose a card number.",
+  "items": {
+    "properties": {
+      "brand": {
+        "description": "Card brand, e.g. \"visa\".",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "expiry": {
+        "description": "Card expiry (MM/YY).",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Vault card ID.",
+        "type": "string"
+      },
+      "label": {
+        "description": "The user's nickname for the card, if any.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "last4": {
+        "description": "Last four digits.",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

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.8/5.0

Behavior5/5

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

Beyond annotations (readOnlyHint=true, idempotentHint=true), the description adds meaningful behavioral context: vault cards never expose a number and pay via device approval, while cards from other apps/companies are read-only in this session. No contradiction with annotations.

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?

The description is information-dense and front-loaded with the core purpose, followed by usage guidance and edge-case behavior. It is longer than ideal but every clause carries useful information, so it earns a 4 rather than a 5.

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?

Despite the tool having zero parameters, the output has complex semantics (wallet vs vaultCards, shared wallet behavior, source tags, read-only restrictions) that the description thoroughly covers. The empty-state action (call create_card) is also addressed, making it complete for an agent.

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 input schema has zero parameters, so schema coverage is trivially 100%. With no parameters to explain, the description correctly focuses on output semantics rather than parameters, deserving the baseline 4 for a no-parameter tool.

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 lists the user's wallet and vault cards, with specific fields (IDs, last four, expiry, balance, status). It distinguishes itself from siblings by noting how vault cards differ and which cards are read-only for get_card_details and close_card.

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 explicitly says 'Start here to find available cards' and provides a conditional alternative: 'if none are returned, call create_card.' It also explains when cards cannot be modified (shared wallet cards from other apps/companies), giving clear when-to-use and when-not 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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?