Skip to main content
Glama

getCurrentUser

Retrieve current user information from the Directus CMS API by providing the API URL and authentication token, simplifying user management through the Directus MCP Server.

Instructions

Get the current user info

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenNoAuthentication token (default from config)
urlNoDirectus API URL (default from config)

Implementation Reference

  • index.ts:440-457 (registration)
    Registration of the 'getCurrentUser' tool in the listTools response, including its input schema definition.
    {
      name: "getCurrentUser",
      description: "Get the current user info",
      inputSchema: {
        type: "object",
        properties: {
          url: { 
            type: "string", 
            description: "Directus API URL (default from config)"
          },
          token: { 
            type: "string", 
            description: "Authentication token (default from config)"
          }
        },
        required: []
      }
    },
  • Handler implementation for 'getCurrentUser' tool. Fetches current user info from Directus API endpoint '/users/me' using axios GET request with bearer token authentication.
    case "getCurrentUser": {
      const token = toolArgs.token || CONFIG.DIRECTUS_ACCESS_TOKEN;
      
      const response = await axios.get(
        `${url}/users/me`,
        { headers: buildHeaders(token) }
      );
      
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2)
          }
        ]
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it 'gets' information (implying read-only), but doesn't mention authentication requirements (despite the token parameter), rate limits, error conditions, or what specific user info is returned. This leaves significant gaps for a tool that likely requires authentication.

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 extremely concise at just 5 words, front-loading the core purpose with zero wasted words. Every element earns its place in this minimal but complete statement of function.

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

Completeness2/5

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

For a tool with no annotations, no output schema, and authentication parameters, the description is insufficient. It doesn't explain what user information is returned, authentication requirements, or how this differs from other user-related tools. The context signals indicate this is incomplete for proper agent understanding.

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?

With 100% schema description coverage, both parameters are already documented in the schema. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline but doesn't enhance understanding of the parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Get') and resource ('current user info'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'getUsers' or 'getItem' which could also retrieve user information, so it doesn't reach the highest score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'getUsers' or 'getItem'. There's no mention of prerequisites, context, or distinctions from sibling tools that also retrieve user data.

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

Related 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/pixelsock/directus-mcp'

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