Skip to main content
Glama

whoami

Read-only

Retrieve the authenticated user's profile including id, name, role, locale, and timezone to resolve 'me' references and identify the acting user.

Instructions

Fetch the authenticated user's profile.

Returns the User you're acting as — id, name, role flags, locale, timezone. Use this to resolve "me" / "myself" references in user requests (assign to meassigned_user_id from this response) or to show the LLM whose perspective it's operating from.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
nameNo
initialsNo
is_account_adminNo
is_account_ownerNo
is_project_managerNo
is_suspendedNo
last_activity_onNo
last_login_atNo
created_atNo
timezoneNo
localeNo
Behavior4/5

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

Adds value beyond the readOnlyHint annotation by detailing the returned fields and use cases. No contradictions with annotations.

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 sentences with minimal redundancy. Front-loaded purpose, then details and usage guidance. Every sentence earns its place.

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?

Fully adequate given zero parameters, an output schema, and the tool's simple nature. Covers purpose, return fields, and usage context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters in the input schema, so the description doesn't need to add semantic meaning. Perfectly fine.

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?

Clearly states it fetches the authenticated user's profile with specific fields (id, name, role flags, locale, timezone). The verb 'fetch' and resource 'profile' are precise, distinguishing it from sibling tools like get_user which likely retrieves other users.

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?

Explicitly describes when to use the tool: to resolve 'me'/'myself' references or to show the LLM's perspective. While it doesn't mention alternatives or when not to use it, the context is clear for a simple identity tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/VeryLongOrgNameSuchWow/kanbantool-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server