Skip to main content
Glama

Get Current User

get_current_user
Read-onlyIdempotent

Retrieve the profile of the user associated with the current API key in MantisBT bug tracker.

Instructions

Retrieve the profile of the user associated with the current API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_current_user' tool, which calls the MantisClient to retrieve the user's profile.
    async () => {
      try {
        const result = await client.get<MantisUser>('users/me');
        return {
          content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
        };
      } catch (error) {
        const msg = error instanceof Error ? error.message : String(error);
        return { content: [{ type: 'text', text: errorText(msg) }], isError: true };
      }
    }
  • Registration of the 'get_current_user' tool within the MCP server.
    server.registerTool(
      'get_current_user',
      {
        title: 'Get Current User',
        description: 'Retrieve the profile of the user associated with the current API key.',
        inputSchema: z.object({}),
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
        },
      },
      async () => {
        try {
          const result = await client.get<MantisUser>('users/me');
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
          };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return { content: [{ type: 'text', text: errorText(msg) }], isError: true };
        }
      }
    );
Behavior3/5

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

Annotations already declare readOnly/idempotent/destructive status. The description adds valuable auth context (API key association) but doesn't elaborate on cache behavior, rate limits, or what profile fields are returned.

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?

Single, dense sentence with zero waste. Information is front-loaded with the action verb, and every clause ('profile', 'current API key') adds necessary semantic value.

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?

Adequate for a zero-parameter read operation with safety annotations. Would benefit from brief mention of what profile data includes since no output schema exists, but 'profile' implies standard user attributes.

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?

Zero parameters present, establishing baseline 4. The description appropriately requires no parameter clarification since the schema is empty.

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?

Excellent specificity: 'Retrieve' (action), 'profile' (resource), and 'user associated with the current API key' (scope) clearly distinguish this from sibling tools like get_project_users or find_project_member.

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 phrase 'associated with the current API key' provides clear context for when to use this (authentication scenarios), though it doesn't explicitly name alternatives like get_project_users for non-current user lookups.

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/dpesch/mantisbt-mcp-server'

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