Skip to main content
Glama
PhononX

Carbon Voice

by PhononX

get_current_user

Read-only

Retrieve your current user profile details from the Carbon Voice platform to access account information and manage conversations.

Instructions

Get the current user information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The inline handler function for the 'get_current_user' tool. It calls the CarbonVoice API's getWhoAmI method with the authentication token to retrieve the current user's information and formats the response using formatToMCPToolResponse.
    async (params: unknown, { authInfo }): Promise<McpToolResponse> => {
      try {
        return formatToMCPToolResponse(
          await cvApi.getWhoAmI(setCarbonVoiceAuthHeader(authInfo?.token)),
        );
      } catch (error) {
        logger.error('Error searching users:', { params, error });
        return formatToMCPToolResponse(error);
      }
    },
  • src/server.ts:388-408 (registration)
    The registration of the 'get_current_user' tool on the MCP server, including the tool name, description, input schema (empty object), annotations, and the inline handler function.
    server.registerTool(
      'get_current_user',
      {
        description: 'Get the current user information. ',
        inputSchema: z.object({}).shape, // Needed in order to have access to authInfo
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
        },
      },
      async (params: unknown, { authInfo }): Promise<McpToolResponse> => {
        try {
          return formatToMCPToolResponse(
            await cvApi.getWhoAmI(setCarbonVoiceAuthHeader(authInfo?.token)),
          );
        } catch (error) {
          logger.error('Error searching users:', { params, error });
          return formatToMCPToolResponse(error);
        }
      },
    );
  • Input schema and metadata for the 'get_current_user' tool: empty input schema (z.object({})), description, and read-only annotation.
    {
      description: 'Get the current user information. ',
      inputSchema: z.object({}).shape, // Needed in order to have access to authInfo
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
      },
    },
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds no behavioral context beyond what annotations provide, such as authentication needs, rate limits, or return format, but it doesn't contradict annotations either.

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, efficient sentence that front-loads the core purpose with no wasted words. It's appropriately sized for a simple tool with no parameters, making it easy for an agent to parse quickly.

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 (0 parameters, annotations covering safety, no output schema), the description is minimally adequate. However, it lacks details on what 'current user information' includes or how it differs from sibling tools, which could help the agent use it more effectively in context.

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?

With 0 parameters and 100% schema description coverage, the schema fully documents the input structure (none required). The description doesn't need to add parameter details, and it appropriately doesn't mention any, earning a baseline score for tools with no 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 information'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_user' or 'search_user', which could retrieve user information in different contexts, 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 'get_user' or 'search_user'. There's no mention of context, prerequisites, or exclusions, leaving the agent to infer usage based on the tool name alone.

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/PhononX/cv-mcp-server'

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