Skip to main content
Glama

system_get_current_user

Returns details about the authenticated user including ID, name, email, permissions, timezone, and default currency to understand session context and permissions.

Instructions

Get information about the currently authenticated user.

Returns complete details about the user associated with the API token, including:

  • User ID, name, and email

  • Account permissions and role

  • Default currency and language

  • Timezone and locale settings

  • Company information

  • Account limits and features

This is useful for understanding the context and permissions of the current API session.

Cached for 60 seconds as user information rarely changes during a session.

Response includes:

  • id: User ID

  • name: Full name

  • email: Email address

  • role_id: User's role ID

  • timezone: User's timezone (e.g., "America/New_York")

  • locale: User's locale (e.g., "en_US")

  • default_currency: Default currency code

  • is_admin: Whether user is an admin

  • activated: Whether account is activated

  • company_id: Company ID

  • company_name: Company name

Common use cases:

  • Get user context for operations

  • Check user permissions

  • Retrieve timezone for date/time operations

  • Get default currency for monetary fields

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations provided, the description fully carries the burden. It confirms the tool is read-only ('Get information'), discloses 60-second caching, and details the response structure, leaving no ambiguity about safety or side effects.

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 well-structured with clear sections and bullet points, making it easy to parse. It could be slightly trimmed without losing information, but it remains effective and comprehensive.

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?

Given the absence of an output schema, the description provides a thorough list of response fields and common use cases. An agent has all necessary information to decide when to call this tool and interpret its results.

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?

The tool has zero parameters and the schema coverage is 100%, so there is no need for additional parameter documentation. The description adds no redundancy and correctly focuses on the output.

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 clearly states it retrieves information about the currently authenticated user, listing specific fields like ID, name, email, permissions, timezone, etc. It distinguishes itself from sibling tools like 'users_get' by focusing on the current user's context without requiring a user ID.

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 description provides explicit use cases (checking permissions, retrieving timezone/currency) and notes caching behavior. While it doesn't explicitly say when not to use it or name alternatives, the context signals are clear enough for an agent to understand its role among siblings.

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/iamsamuelfraga/mcp-pipedrive'

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