Skip to main content
Glama
delano
by delano

get_authenticated_user

Get information about the authenticated user in Postman. Use this to confirm identity and access permissions.

Instructions

Get authenticated user information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the 'get_authenticated_user' tool logic. It calls GET /me on the Postman API client and returns the authenticated user information.
    /**
     * Get authenticated user information
     * Returns different response for Guest and Partner roles
     * Returns flow_count only for Free plan users
     */
    async getAuthenticatedUser(): Promise<ToolCallResponse> {
      const response = await this.client.get('/me');
      return this.createResponse(response.data);
    }
  • Routes the 'get_authenticated_user' tool name to the getAuthenticatedUser() handler via a switch statement in handleToolCall.
    case 'get_authenticated_user':
      return await this.getAuthenticatedUser();
  • The schema definition for the 'get_authenticated_user' tool. It has no required input fields (empty properties object).
    {
      name: 'get_authenticated_user',
      description: 'Get authenticated user information',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [] // No required fields
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only states 'Get', implying read-only, but does not mention any details about authentication requirements, response format, or any potential 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, no unnecessary words. It is concise and front-loaded.

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?

Given no parameters and no output schema, the description provides sufficient high-level information. However, it could briefly state the type of information returned.

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 input schema has no parameters, so schema coverage is 100%. The description does not need to add parameter information. Baseline for 0 parameters is 4.

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 the resource 'authenticated user information', which is specific. However, it does not differentiate from similar sibling tools like get_user_info or get_accounts.

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?

No guidance is provided on when to use this tool versus alternatives. There is no indication of context or prerequisites.

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/delano/postman-mcp-server'

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