Skip to main content
Glama

Show my passport and balance

whoami
Read-only

Show your passport, how strong this sign-in is (credential), balance (owner.balance_expires_at: when it expires without a top-up or purchase; tell your human in time), starter credit (owner.starter_credit: what is left of the free start's credit and until when; buy spends it first, even at a balance of 0, on a new utility or code kit it covers in full; starter_status shows the free start itself), spend limit, notices, pending reviews, and at most one optional question from us (answer it once with send_feedback and its prompt_id). owner.email_hint (who paid, masked) and owner.passport_count show who is behind your balance: if they are not your human's, tell your human (as your owner's only agent you may also call leave_owner). owner.notices lists agents that joined (also with a code from your owner's email), tokens that spent from a new network, and lockdowns.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "whoami"
  }
}

Input Schema

NameRequiredDescriptionDefault
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {}
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / passport_token / description
      Previous value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."
  4. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the readOnlyHint and non-destructive annotations, the description explains important semantics: balance expiration timing, starter credit being spent first even at zero balance, masked owner hints, passport count ownership implications, and the kinds of events in notices. It also tells the agent to alert its human about expiring balance or mismatched ownership, which is valuable behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is information-dense and mostly earns its place, but it is delivered as a single run-on paragraph with nested parentheticals that make it harder to scan. It would be more effective if the output fields and follow-up actions were separated into clearer clauses.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a status tool with no output schema, the description does a thorough job naming the returned fields and their meaning, including expiration and ownership-related data. It omits no critical calling instructions, though the dense presentation slightly reduces usability.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The sole optional parameter has 100% schema description coverage explaining the passport_token fallback when no app sign-in header is available. The description does not add further meaning beyond the schema, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies a read-only status tool that shows the agent's passport, credential strength, balance, starter credit, limits, notices, reviews, and optional question. It distinguishes itself from siblings by naming send_feedback and leave_owner for specific follow-up actions, though the opening sentence is a dense list rather than a sharp single-purpose statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the enumeration of status fields, but there is no explicit 'use this when you need to check status' or when-not guidance against tools like starter_status or buy. It does give useful situational guidance: answer the optional question once with send_feedback and prompt_id, and call leave_owner if the masked owner identity is not your human's.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.