Skip to main content
Glama

Identify the calling principal

whoami
Read-onlyIdempotent

Returns the caller's identity, org, role, role-derived RBAC capabilities, and token scopes. Use this to check whether the current token may perform an action (e.g. config:write) before attempting it.

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

No arguments

Output Schema

NameRequiredDescriptionDefault
roleYes
orgIdYes
scopesYes
userIdYes
projectIdYesThe project this credential is bound to, or null when it is org-wide. A bound token can read and act only on that project, and on nothing org-wide - so a caller can see the boundary it works within rather than discovering it through a 404.
capabilitiesYes
principalTypeYesagent: a self-registered agent nobody has claimed yet. It has no user, org, role or scopes, and reaches only /me and /scopes until a person claims it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / capabilities / items / enum
      Previous value: -[
      -  "pipeline:control",
      -  "config:write",
      -  "secrets:reveal",
      -  "org:admin",
      -  "billing:manage"
      -]New value: +[
      +  "pipeline:control",
      +  "config:write",
      +  "secrets:reveal",
      +  "org:admin",
      +  "billing:manage",
      +  "site-data:read",
      +  "site-data:write"
      +]
  2. First observed

TDQS

A4.5/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 safety is covered. The description adds genuine context beyond them: the payload includes role-derived RBAC capabilities and token scopes, and those are meant to be used as a pre-flight permission gate for other actions.

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?

Two tight sentences: the first declares the return payload, the second declares the operational use. Front-loaded, zero filler, nothing repeated from the schema or annotations.

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-param read-only tool with full annotation coverage and an output schema, the description supplies everything an agent needs: what comes back and why to call it. No gaps remain that the structured fields do not already fill.

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 takes zero parameters, so there is no parameter semantics to document; the baseline applies. The description correctly implies no inputs are required to scope the query to the current token.

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 ('Returns') and enumerates the exact resource fields: caller identity, org, role, RBAC capabilities, and token scopes. No sibling tool covers this, and an agent can tell instantly this is the identity/introspection endpoint.

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?

Gives an explicit precondition pattern: call this to check whether the token may perform an action (e.g. config:write) before attempting it. Clear when-to-use, but no when-not guidance or named alternative for related introspection needs.

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.