Skip to main content
Glama

Get user detail

get_user
Read-onlyIdempotent

Fetch a user's profile to verify account status, admin flag, and contact details before assigning work or checking administrator privileges.

Instructions

Read one user's profile: name, login, email, admin flag and status.

Use it after search_principals when you need more than a name — to confirm an account is active before assigning work, to check whether somebody is an instance administrator, or to learn which account the server itself is acting as (id_or_me='me').

Returns {id, name, login, email, admin, status, language, created_at, updated_at}. The avatar URL is deliberately dropped: it costs tokens and cannot be rendered here.

Pitfalls. email, login and admin are visibility-dependent — a null means the authenticated account may not see that field, never that the value is empty. admin=true says nothing about project permissions; use list_permissions for what the current user may actually do. A group or placeholder-user id returns 404 from this endpoint; those principals only appear in search_principals.

Cross-references: search_principals to find the id; list_memberships(principal_id=...) for the projects and roles this person holds; get_instance_info also reports the current user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
id_or_meYesNumeric user id from search_principals, or the literal string 'me' for the account this server authenticates as. Group and placeholder ids are not accepted here — this endpoint serves users only.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoNumeric user id.
nameNoDisplay name, e.g. 'Grace Hopper'.
adminNoTrue for instance administrators. Null when the field is not visible to the caller — treat null as 'unknown', never as 'not an admin'.
emailNoEmail address; null when the authenticated account may not see it.
loginNoLogin name used to sign in.
statusNoAccount status, one of: active, invited, registered, locked.
languageNoInterface language code, e.g. 'en'. Absent on some instances.
created_atNoISO 8601 UTC timestamp.
updated_atNoISO 8601 UTC timestamp.
Behavior5/5

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

The description adds significant context beyond annotations: visibility-dependent nulls, the deliberate dropping of avatar URL, 404 behavior for group/placeholder ids, and the meaning of 'me'. No contradiction with readOnlyHint=true or other annotations.

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?

The description is thorough and organized with a clear opening, a usage paragraph, a return-value line, a pitfalls section, and cross-references. It is longer than necessary but every sentence adds value; front-loaded with the core purpose.

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 description is complete for a simple read tool: it covers what fields are returned, visibility caveats, error behavior (404), idempotency context, and direct alternatives. The presence of an output schema and supportive annotations further reduces ambiguity.

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 coverage is 100%, so the baseline is 3. The description reinforces the parameter's dual type (integer or 'me') and mentions the restriction on group ids, but the schema already captures these details. No substantial additional parameter semantics are provided.

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?

The description opens with a specific verb+resource ('Read one user's profile') and lists concrete fields (name, login, email, admin flag, status). It clearly distinguishes itself from siblings by referencing search_principals (which returns only names) and list_permissions (for project permissions).

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?

Explicit usage guidance is provided: 'Use it after search_principals when you need more than a name' with concrete scenarios (confirm active account, check admin, use 'me'). It also gives an exclusion ('admin=true says nothing about project permissions; use list_permissions') and cross-references other tools.

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/kar-thik/openproject-mcp'

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