Skip to main content
Glama
AgenticMail

AgenticMail

Official
by agenticmail

whoami

Retrieve the current AI agent's account profile — name, email, role, and metadata — to confirm which identity an AgenticMail session is authenticated as.

Instructions

Get the current agent's account info — name, email, role, and metadata

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

NameRequiredDescriptionDefault
_accountNoOptional. Override identity for THIS call: pass the AgenticMail agent name (e.g. "Fola") to authenticate as that agent. Requires AGENTICMAIL_ACCOUNT_KEYS_JSON to contain a matching key. Omit to use the default identity (AGENTICMAIL_API_KEY).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.104
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv0.9.101
  3. Removedv0.9.89
  4. Addedv0.9.73
  5. Removedv0.9.69
  6. Addedv0.9.35
  7. Removedv0.9.31
  8. Addedv0.9.12
  9. Removedv0.9.11
  10. Changed2 schema fields changedv0.5.63
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / _account
      Added value: +{
      +  "description": "Optional. Override identity for THIS call: pass the AgenticMail agent name (e.g. \"Fola\") to authenticate as that agent. Requires AGENTICMAIL_ACCOUNT_KEYS_JSON to contain a matching key. Omit to use the default identity (AGENTICMAIL_API_KEY).",
      +  "type": "string"
      +}
  11. First observedv0.5.59

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the shape of the result (name, email, role, metadata), which is genuinely useful. However it says nothing about the read-only nature, the authentication behavior of the _account override, or failure modes when a key is missing.

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?

One front-loaded sentence with zero filler; the returned fields are listed immediately after the core purpose. Nothing could be removed without losing information.

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 simple identity read with one optional, well-documented parameter, the description covers purpose and return contents adequately. It falls slightly short only because there is no output schema and it does not explain behavior when the _account override is used.

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?

Schema description coverage is 100% and the single optional _account parameter is fully documented in the schema, including the required environment variable. The description adds no parameter meaning, so the baseline 3 applies.

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?

States a specific verb and resource ('Get the current agent's account info') and enumerates the returned fields (name, email, role, metadata), which separates it from sibling tools like list_agents or create_account. It is clear what the tool does, though it never explicitly names an alternative.

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

Usage Guidelines2/5

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

The phrase 'current agent's' hints at self-identity lookup, but there is no explicit statement of when to use this versus list_agents or other identity-related siblings, and no preconditions are given. Usage must be inferred from the purpose statement alone.

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