Skip to main content
Glama

Hail Communication for AI

Who am I

whoami
Read-onlyIdempotent

Identify the account and organization authorized by the current credentials.

    Returns ``auth_kind``, ``organization_id``, ``user_id``, ``email`` and ``name``.
    Shared operator credentials have ``auth_kind="shared"`` with null user details.
    The response identifies the current actor, not a message recipient.

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
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Model ID of the calling agent. Optional. Recorded for analytics only.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: shared operator credentials yield auth_kind="shared" with null user details, which tells the agent to expect a valid-but-anonymous response instead of an error.

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?

Four short sentences, front-loaded with the purpose, then the disambiguating caveat last. The field enumeration partially duplicates the output schema, which is the only mild redundancy; nothing else is wasted.

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?

The tool has an output schema and full annotation coverage, so the description only needs to supply the edge cases — and it does, covering both the shared-credential null-detail case and the actor-versus-recipient interpretation. Nothing an agent needs to call this correctly is missing.

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 parameter (llm_model, optional, analytics-only) is fully documented in the schema. The description adds nothing about it, which is acceptable but earns only the baseline for a high-coverage schema.

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?

States a specific verb and resource: 'Identify the account and organization authorized by the current credentials.' It also explicitly scopes what the result means ('the current actor, not a message recipient'), so an agent can instantly tell this apart from any message-recipient lookup.

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

Usage Guidelines4/5

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

The closing sentence gives a clear usage boundary — use this to resolve the acting identity, not to resolve who a message is addressed to. That is a real disambiguation for an agent inspecting inbound message metadata. It stops short of naming an alternative tool or listing when-not-to-call, so it isn't a full 5.

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.

Resources