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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON 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, or organization through a company's app.
`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.
`connectionOrganizationId`	No	Organization id, when connectionType is organization.

Schema Changelog

Changes observed during successful MCP inspections.

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

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description's 'Read-only' is consistent with those. However, the description adds valuable non-obvious context beyond the annotations: KYC data is a stored snapshot rather than live, and session connectivity details (personal login vs third-party OAuth app) are disclosed.

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 front-loaded with purpose, then moves to usage triggers, then safety, then the KYC caveat and sibling routing. It is compact yet information-dense; every sentence earns its place and no filler is present.

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 tool with an output schema present, the description covers everything an agent needs: what the tool returns, when to call it, the read-only safety profile, the stored-snapshot limitation, and the alternative for live KYC. No material gap remains.

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 zero parameters and an empty input schema, so 100% schema coverage is automatic and there is nothing for the description to add. This matches the 0-param baseline, where parameter semantics are inherently satisfied.

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 opens with a specific verb and resource ('Show who you are operating as') and enumerates the exact fields returned: email, user id, name, plan, KYC + account status, member-since date, and session connection type. It also distinguishes this tool from get_kyc_status by clarifying the stored-snapshot vs live-state difference, so an agent can tell it apart from siblings without opening schemas.

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?

The description gives explicit trigger conditions: call when the user asks 'who am I' / 'which account is this', or before money-moving actions when account confirmation is needed. It also provides a direct alternative with a selection rule: use get_kyc_status when the live, provider-checked KYC state is required instead of the stored snapshot.

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?