agentcard

get_wallet_link

The user's hosted wallet, as one shareable URL. Opens their Agentcard wallet in the browser: every card in one place, apply for an Agentcard card (identity verification runs right in the page). Mint it whenever the user needs a browser step (seeing cards, finishing verification when in-chat photos fail) and send them the URL. To ADD the user's own card, pass purpose "add_card": the link then opens their Agentcard vault card form directly (any card, typed once, locked with their passkey or master password, never seen by Agentcard) and works on personal logins too. Pass merchant + amount_cents to open the wallet ON the payment-approval sheet (the user picks a card and approves that exact charge) instead of the card list. Multi-use but short-lived (about 15 minutes — the exact moment is in expiresAt); mint a fresh one when it expires. The wallet link only works for app connections (OAuth).

Input Schema

TableJSON Schema

Name	Required	Description
`purpose`	No	"wallet" (default) opens the hosted wallet. "add_card" opens the vault card form so the user can put their own card on file; single-use, about 15 minutes.
`merchant`	No	Merchant name shown on the payment-approval sheet (with amount_cents).
`amount_cents`	No	Amount in cents. When present, the link opens on the payment-approval sheet for this charge.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	No	The hosted wallet URL to share with the user.
`kind`	No	purpose add_card only: how the vault link signs the user in. "connected" = a one-time code to their own phone or email; "handoff" = directly; "open" = passkey setup or passkey sign-in.
`message`	Yes	Ready-to-send sentence containing the URL.
`sandbox`	No	True when the connection is in test mode.
`expiresAt`	No	ISO time the link stops working.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 16, 2026

changedOutput schema / properties / kind / description

Previous value: -"purpose add_card only: how the vault link signs the user in. \"connected\" = a one-time code to their own phone or email; \"handoff\" = directly; \"open\" = Face ID setup or passkey sign-in."New value: +"purpose add_card only: how the vault link signs the user in. \"connected\" = a one-time code to their own phone or email; \"handoff\" = directly; \"open\" = passkey setup or passkey sign-in."

Changed2 schema fields changedSep 7, 2026

addedInput schema / properties / purpose

Added value: +{
+  "description": "\"wallet\" (default) opens the hosted wallet. \"add_card\" opens the vault card form so the user can put their own card on file; single-use, about 15 minutes.",
+  "enum": [
+    "wallet",
+    "add_card"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / kind

Added value: +{
+  "description": "purpose add_card only: how the vault link signs the user in. \"connected\" = a one-time code to their own phone or email; \"handoff\" = directly; \"open\" = Face ID setup or passkey sign-in.",
+  "type": "string"
+}

Changed2 schema fields changedAug 14, 2026

addedInput schema / properties / amount_cents

Added value: +{
+  "description": "Amount in cents. When present, the link opens on the payment-approval sheet for this charge.",
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / merchant

Added value: +{
+  "description": "Merchant name shown on the payment-approval sheet (with amount_cents).",
+  "type": "string"
+}

AddedAug 13, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the all-false annotations, the description discloses substantial behavior: the link opens in a browser, identity verification runs in the page, add_card data is never seen by Agentcard, the link is multi-use but short-lived (~15 minutes with exact time in expiresAt), and it requires OAuth. This gives the agent a full safety and lifecycle picture.

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 dense but every sentence carries necessary information: core purpose, when to use, parameter-specific behaviors, expiry, and the OAuth constraint. The most important information is front-loaded, and the length is justified by the tool's multiple modes.

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?

With an output schema present, return values need no explanation. The description covers all three invocation modes, the exact use cases, the short-lived nature and expiry handling, and the OAuth limitation. Nothing an agent needs to decide when and how to call it 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 100%, but the description adds meaning beyond the schema: it explains that 'wallet' is the default, 'add_card' opens the vault form and works on personal logins, and merchant + amount_cents together open the payment-approval sheet. This is exactly the semantic enrichment needed for correct invocation.

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 states a specific deliverable ('the user's hosted wallet, as one shareable URL') and a clear verb ('Mint it'). It distinguishes three distinct modes (wallet, add_card, payment approval), so an agent can tell it apart from sibling card/wallet tools.

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 when to use the tool ('whenever the user needs a browser step (seeing cards, finishing verification when in-chat photos fail)') and gives specific conditions for each parameter combination. It also states a hard constraint ('only works for app connections (OAuth)'), effectively telling the agent when not to use it.

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?