agentcard

whoami

Read-onlyIdempotent

Show who you are operating as: the authenticated AgentCard account's email, user id, name, plan, KYC + account status, member-since date, and how this session is connected (personal login vs a third-party OAuth app connection, with the app name). Call this when the user asks "who am I" / "which account is this", or before money-moving actions when you need to confirm the account. Read-only. KYC shown here is the stored snapshot — use get_kyc_status when you need the live, provider-checked state.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`name`	No	Cardholder name ("First Last"), or null before KYC info is submitted.
`plan`	No	Subscription plan id, e.g. 'free', 'basic', or 'pro'.
`email`	No	Email of the authenticated account, or null for a phone-first account (e.g. signed up by text message).
`userId`	No	AgentCard user id of the authenticated account.
`message`	Yes	Human-readable identity summary.
`kycStatus`	No	Raw stored KYC state (e.g. approved, pending, requires_input), or null if never started.
`kycVerified`	No	Whether identity verification (KYC) has passed (stored snapshot).
`memberSince`	No	ISO timestamp the account was created.
`accountStatus`	No	Account standing: 'active' or 'suspended'.
`connectionType`	No	How this session authenticates: 'oauth' (third-party app connection), 'personal' (CLI/dashboard login), or 'organization' (a company's Agentcard integration acting for its end user).
`connectionClientId`	No	OAuth client id of the connected app, when connectionType is oauth. Null for a company connection.
`subscriptionStatus`	No	Stripe subscription status (e.g. 'active', 'past_due'), or null on the free plan.
`connectionClientName`	No	Display name of the connected OAuth app (e.g. "Claude"), when known, for an oauth or organization connection.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 7, 2026

changedOutput schema / properties / connectionClientId / description

Previous value: -"OAuth client id of the connected app, when connectionType is oauth, or organization through a company's app."New value: +"OAuth client id of the connected app, when connectionType is oauth. Null for a company connection."

removedOutput schema / properties / connectionOrganizationId

Removed value: -{
-  "description": "Organization id, when connectionType is organization.",
-  "type": [
-    "string",
-    "null"
-  ]
-}

Changed2 schema fields changedSep 25, 2026

changedOutput schema / properties / connectionClientId / description

Previous value: -"OAuth client id of the connected app, when connectionType is oauth."New value: +"OAuth client id of the connected app, when connectionType is oauth, or organization through a company's app."

changedOutput schema / properties / connectionClientName / description

Previous value: -"Display name of the connected OAuth app (e.g. \"Claude\"), when known."New value: +"Display name of the connected OAuth app (e.g. \"Claude\"), when known, for an oauth or organization connection."

Changed1 schema field changedSep 16, 2026

changedOutput schema / properties / email / description

Previous value: -"Email of the authenticated account, or null for a phone-first account (e.g. signed up by SMS on the iMessage relay)."New value: +"Email of the authenticated account, or null for a phone-first account (e.g. signed up by text message)."

First observedJul 28, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the standalone 'Read-only.' sentence is redundant. However, the description adds genuinely new behavioral context: that the session connection type (personal login vs third-party OAuth app, with app name) is surfaced, and that the KYC value is a cached snapshot rather than live data — a meaningful caveat for a read tool.

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?

Three sentences, front-loaded with the resource description before use cases and caveats. The single-word 'Read-only.' sentence duplicates the annotation and could be cut, but otherwise every clause carries information.

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?

For a zero-parameter read tool with annotations and an output schema, this is complete: the agent knows what it returns, when to call it, when to prefer a sibling, and the snapshot-vs-live KYC caveat that would otherwise cause a wrong KYC reading.

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 there is nothing for the description to disambiguate and the baseline applies. The description instead characterizes the shape of the returned identity record, which is useful even though a separate output schema exists.

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 names a specific verb ('Show who you are operating as') and enumerates exactly what identity data comes back: email, user id, name, plan, KYC/account status, member-since, and connection type. It also distinguishes itself from get_kyc_status by scoping the KYC field to a stored snapshot.

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 two concrete triggers ('who am I' / 'which account is this' questions, and pre-money-movement verification) and explicitly routes the agent to get_kyc_status when a live provider-checked KYC state is needed. Alternatives and exclusions are both stated.

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?