Skip to main content
Glama
MikelA92

Metabase MCP Server

by MikelA92

get_current_user

Retrieve details about the currently authenticated Metabase user, including identity and permissions, for secure access control and personalized data interaction.

Instructions

👤 [SAFE] Get information about the currently authenticated user (you). Risk: None - read-only operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that executes the get_current_user tool logic by fetching the current user from Metabase API and formatting the response.
      async getCurrentUser() {
        this.logger.debug('Getting current user');
        const user = await this.apiClient.makeRequest('/api/user/current');
        
        return {
          content: [
            {
              type: 'text',
              text: `Current User:
    ID: ${user.id}
    Name: ${user.common_name}
    Email: ${user.email}
    Is Admin: ${user.is_superuser}`,
            },
          ],
        };
      }
  • The tool schema definition specifying the name, description, and empty input schema (no parameters required). Used for tool listing and validation.
      name: 'get_current_user',
      description: '👤 [SAFE] Get information about the currently authenticated user (you). Risk: None - read-only operation.',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Registration/dispatch point in the main server switch statement that routes tool calls to the userHandlers.getCurrentUser method.
    case 'get_current_user':
      return await this.userHandlers.getCurrentUser();
Behavior5/5

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

With no annotations provided, the description carries full burden and excels by explicitly stating the safety profile ('[SAFE]', 'Risk: None - read-only operation'). This clearly communicates the tool's non-destructive, permission-required nature, going beyond what the input schema alone would indicate.

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?

The description is perfectly front-loaded with the core purpose first, followed by critical safety information. Every sentence earns its place - the emoji adds visual distinction, the safety declaration is essential given no annotations, and the risk statement provides valuable context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read-only tool with no output schema, the description provides excellent coverage of purpose and safety. The main gap is not describing the return format or what user information is included, but given the tool's simplicity and clear safety declaration, this is a minor omission.

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 has zero parameters with 100% schema description coverage, so the baseline would be 4. The description appropriately doesn't discuss parameters since none exist, maintaining focus on the tool's purpose and behavior.

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 the specific action ('Get information') and target resource ('currently authenticated user'), with the parenthetical '(you)' adding helpful clarification. It distinguishes this from sibling tools like 'list_users' by focusing on the current user rather than listing all 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?

The description provides clear context about when to use this tool ('Get information about the currently authenticated user'), but doesn't explicitly mention when not to use it or name specific alternatives. It implies usage for retrieving self-information rather than querying other users.

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/MikelA92/metabase-mcp-mab'

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