Skip to main content
Glama

current_user

Access detailed information about the currently authenticated user within your Vaiz workspace.

Instructions

Get detailed information about current authenticated user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool schema definition for 'current_user' - defines the tool with no required input parameters, returning information about the current authenticated user
    {
      name: 'current_user',
      description:
        'Get detailed information about current authenticated user',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Tool handler registration in proxy server - all tool calls (including 'current_user') are proxied to the remote API via the CallToolRequestSchema handler. No specific local handler exists; the tool is forwarded to the backend.
    private registerHandlers(): void {
      const lowLevel = this.mcpServer.server;
    
      lowLevel.setRequestHandler(ListToolsRequestSchema, async () => {
        this.log('← tools/list');
        try {
          const result = (await this.proxyToRemote('tools/list')) as {
            tools?: Tool[];
          };
          const remoteTools = result?.tools ?? [];
          return { tools: mergeByName(VAIZ_TOOLS, remoteTools) };
        } catch {
          const cached = this.responseCache.get('tools/list') as {
            tools?: Tool[];
          } | undefined;
          return {
            tools: mergeByName(VAIZ_TOOLS, cached?.tools ?? []),
          };
        }
      });
    
      lowLevel.setRequestHandler(CallToolRequestSchema, async (request) => {
        this.log(`← tools/call ${request.params.name}`);
        const result = await this.proxyToRemote('tools/call', request.params);
        return result as { content: Array<{ type: string; text: string }> };
      });
  • The mergeByName helper is used to merge hardcoded tool definitions (including 'current_user') with remote tool definitions at runtime.
    function mergeByName<T extends { name: string }>(
      hardcoded: T[],
      remote: T[],
    ): T[] {
      const map = new Map<string, T>();
      for (const item of hardcoded) map.set(item.name, item);
      for (const item of remote) map.set(item.name, item);
      return [...map.values()];
    }
    
    function mergeByUri(
      hardcoded: Resource[],
      remote: Resource[],
    ): Resource[] {
      const map = new Map<string, Resource>();
      for (const item of hardcoded) map.set(item.uri, item);
      for (const item of remote) map.set(item.uri, item);
      return [...map.values()];
    }
Behavior3/5

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

With no annotations, the description carries the full burden. It correctly identifies the operation as a read but lacks details on the response format, authentication requirements, or any potential errors. 'Detailed information' is vague but adequate for a simple getter.

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 that efficiently conveys the tool's purpose without unnecessary words.

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

Completeness5/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, low complexity), the description is complete. It fully informs what the tool does without needing additional details.

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 zero parameters, so schema coverage is 100%. The description adds no parameter information, which is acceptable since no parameters exist. Baseline 4 applies.

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 specifies the verb 'Get' and the resource 'current authenticated user', distinguishing it from sibling tools that focus on other entities like tasks, projects, or members.

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?

No explicit when-to-use guidance is provided, but the tool's simplicity (zero parameters, single purpose) makes its usage obvious. It implicitly contrasts with sibling tools that have different scopes or require parameters.

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/vaizcom/vaiz-mcp'

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