Skip to main content
Glama

whoami

Read-onlyIdempotent

Who you are and how posterly is connected. view=identity (default): the authenticated user, API key scopes, workspaces, and onboarding next step. Pass include=api_keys to also list this account's API keys (name, prefix, scopes, created, last used). The secret is never included. Call this first. If onboarding.completed is false, call complete_onboarding (name and IANA timezone) IN THIS chat before scheduling, never via /onboarding-v2; if true, never ask again. view=status: hosted MCP server version, latest npm version for local app clients, endpoint and API auth health, and update guidance.

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
viewNoidentity (default): user, scopes, workspaces, onboarding. status: MCP server and connection health.identity
includeNoidentity only. api_keys lists this account's API keys. The secret is never included. Omit it for the usual identity answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include
      Added value: +{
      +  "description": "identity only. api_keys lists this account's API keys. The secret is never included. Omit it for the usual identity answer.",
      +  "enum": [
      +    "api_keys"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description still adds real behavioral context beyond them: the API key secret is never included in output, include=api_keys is identity-only, and the onboarding flag drives a required follow-up flow. It stops short of five because return-value detail overlaps what would normally be output-schema content.

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?

Front-loaded with purpose, then per-view semantics, then the call-first directive. Dense but every sentence carries operational information; the only weakness is that the important "Call this first" directive sits mid-paragraph rather than leading the description.

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?

There is no output schema, so the description carries the return-shape burden and does it for both views, plus the security caveat about secrets and the onboarding branch. For a two-param, zero-required read tool, nothing an agent needs is missing.

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?

Schema coverage is 100% with enum descriptions, so the baseline is 3. The description goes further by naming the default behavior of view, scoping include=api_keys to identity only, listing the fields it returns (name, prefix, scopes, created, last used), and telling the agent to omit it for the usual answer.

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 resource (the authenticated identity and connection state) with an explicit two-mode split: view=identity for user, scopes, workspaces, onboarding next step; view=status for server version, endpoint and auth health. An agent can tell exactly what it gets without opening the schema.

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?

Explicitly says "Call this first" and then branches on the result: if onboarding.completed is false, call complete_onboarding in this chat before scheduling, never via /onboarding-v2; if true, never ask again. That is concrete when-to-use, when-to-follow-up, and an explicit anti-pattern to avoid.

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