Skip to main content
Glama

show_currentuser

Retrieves and displays information about the currently authenticated user in the Anaplan system.

Instructions

Get current authenticated user info

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler for 'show_currentuser' - calls apis.users.getCurrentUser() and formats the response as text.
    server.tool("show_currentuser", "Get current authenticated user info", {}, async () => {
      const user = await apis.users.getCurrentUser();
      const lines = [
        `**Name:** ${user.firstName} ${user.lastName}`,
        `**Email:** ${user.email}`,
        `**ID:** ${user.id}`,
        `**Active:** ${user.active}`,
        `**Last Login:** ${user.lastLoginDate ?? "N/A"}`,
      ];
      return { content: [{ type: "text" as const, text: lines.join("\n") }] };
    });
  • Schema for 'show_currentuser' - empty object {}, no parameters required.
    server.tool("show_currentuser", "Get current authenticated user info", {}, async () => {
  • Tool registration via server.tool('show_currentuser', ...) inside registerExplorationTools.
    server.tool("show_currentuser", "Get current authenticated user info", {}, async () => {
      const user = await apis.users.getCurrentUser();
      const lines = [
        `**Name:** ${user.firstName} ${user.lastName}`,
        `**Email:** ${user.email}`,
        `**ID:** ${user.id}`,
        `**Active:** ${user.active}`,
        `**Last Login:** ${user.lastLoginDate ?? "N/A"}`,
      ];
      return { content: [{ type: "text" as const, text: lines.join("\n") }] };
    });
  • src/server.ts:54-57 (registration)
    Call to registerExplorationTools which registers 'show_currentuser' on the server.
    registerExplorationTools(server, {
      workspaces, models, modules, lists, imports, exports, processes, files, actions, transactional, modelManagement, dimensions,
      calendar, versions, users,
    }, resolver);
  • getCurrentUser() API method that performs GET /users/me to fetch the current user.
    async getCurrentUser() {
      const res = await this.client.get<any>("/users/me");
      return res.user ?? res;
    }
Behavior3/5

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

The description implies a read-only operation ('Get'), but no annotations exist to confirm safety. It does not disclose authentication requirements, potential errors, or return format, which is a minor gap for a simple tool.

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?

A single concise sentence with no wasted words. Perfectly sized for a simple tool.

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

Completeness3/5

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

Given the tool's simplicity (no parameters, no output schema, no annotations), the description is adequate but lacks details on return value behavior or error handling, leaving some ambiguity.

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, and the input schema covers 100% of nothing. The description adds no parameter information, but none is needed. Baseline of 4 is appropriate.

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 'Get current authenticated user info' clearly specifies the action (get) and the resource (current authenticated user info), distinguishing it from sibling tools like 'show_users' which lists 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'show_users' or 'show_userdetails'. While the purpose is clear, explicit usage context is missing.

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/larasrinath/anaplan-mcp'

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