Skip to main content
Glama

whoami

Read-onlyIdempotent

Retrieves your current user and workspace details—IDs, name, role, plan days left, and storage—so you can identify yourself as owner, assignee, or message sender.

Instructions

Current user and workspace: ids, name, role, plan days left, storage.

Call first when you need your own user id (it appears as owner / assignee / message sender elsewhere).

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, and an output schema exists, so the safety profile and return shape are covered elsewhere. The description adds one genuinely useful behavioral fact: the returned id is the same identifier used as owner/assignee/sender in other data. That is helpful context but modest, so a 3 rather than higher.

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 short sentences, front-loaded with the returned data and followed by the actionable usage cue. Nothing is wasted and nothing important is buried.

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 trivial parameterless read with full annotation coverage and an output schema, the description supplies everything an agent needs: what comes back and why to call it early. No missing prerequisite or ambiguity remains.

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 nothing for the description to disambiguate. The baseline for a parameterless tool applies, and the description doesn't confuse the issue.

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 tool enumerates what it returns: user and workspace ids, name, role, plan days left, and storage. That is concrete and specific for a no-parameter identity lookup. It doesn't name a sibling to contrast with, but no sibling in the list is an identity tool, so the ambiguity risk is low.

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 second sentence gives explicit guidance: call it first when you need your own user id, and it explains why (the id appears as owner / assignee / message sender elsewhere). It does not name an alternative tool or a when-not-to-use case, which keeps it short of a 5.

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