Skip to main content
Glama
PhononX

Carbon Voice

by PhononX

get_message

Read-only

Retrieve a specific message from Carbon Voice conversations using its unique ID, with options to include related data like conversation context or creator information.

Instructions

Get a message by its ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
languageNoLanguage (optional) - Original language will be used if not provided or not found.
fieldsNoFields (optional) - Additional fields to include in the response. Possible values: conversation, creator, labels.

Implementation Reference

  • src/server.ts:126-151 (registration)
    Registration of the 'get_message' MCP tool, including description, input schema (merged zod schemas), annotations, and the inline handler function that delegates to simplifiedApi.getMessageById with authentication.
    server.registerTool(
      'get_message',
      {
        description: 'Get a message by its ID.',
        inputSchema: getMessageByIdParams.merge(getMessageByIdQueryParams).shape,
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
        },
      },
      async (args: GetMessageInput, { authInfo }): Promise<McpToolResponse> => {
        try {
          const { id, ...queryParams } = args;
          return formatToMCPToolResponse(
            await simplifiedApi.getMessageById(
              id,
              queryParams,
              setCarbonVoiceAuthHeader(authInfo?.token),
            ),
          );
        } catch (error) {
          logger.error('Error getting message by id:', { args, error });
          return formatToMCPToolResponse(error);
        }
      },
    );
  • Zod schemas defining the input parameters for getMessageById: path param 'id' and optional query params 'language' and 'fields'. These are merged for the tool's inputSchema.
    export const getMessageByIdParams = zod.object({
      "id": zod.string()
    })
    
    export const getMessageByIdQueryParams = zod.object({
      "language": zod.string().optional().describe('Language (optional) - Original language will be used if not provided or not found.'),
      "fields": zod.string().optional().describe('Fields (optional) - Additional fields to include in the response. Possible values: conversation, creator, labels.')
    })
  • The underlying API handler getMessageById that makes the HTTP GET request to retrieve the message by ID using the mutator function, called by the MCP tool handler.
    const getMessageById = (
      id: string,
      params?: GetMessageByIdParams,
      options?: SecondParameter<typeof mutator>,
    ) => {
      return mutator<GetMessageResponse>(
        { url: `/simplified/messages/${id}`, method: 'GET', params },
        options,
      );
    };
  • TypeScript interface for the GetMessageResponse, defining the structure of the tool's output including message, optional creator, conversation, and labels.
    export interface GetMessageResponse {
      message: Message;
      creator?: User;
      conversation?: Conversation;
      labels?: Label[];
    }
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 doesn't add any behavioral context beyond what annotations provide—no mention of authentication requirements, rate limits, error conditions, or response format. However, it doesn't contradict the 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, clear sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple retrieval tool. Every word earns its place without being overly terse.

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?

For a simple read operation with good annotations (readOnlyHint, destructiveHint) and moderate schema coverage, the description is minimally adequate. However, without an output schema, the description doesn't explain what the tool returns (message content, metadata, etc.), leaving a gap in understanding the result. The context signals suggest this is a straightforward tool, but the description could be more complete.

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?

Schema description coverage is 67% (2 out of 3 parameters have descriptions). The description doesn't add any parameter semantics beyond what's in the schema—it mentions the 'id' parameter implicitly but provides no additional context about format, validation, or usage. With moderate schema coverage, the baseline 3 is appropriate as the description doesn't compensate for gaps.

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 action ('Get') and resource ('a message by its ID'), making the purpose immediately understandable. It distinguishes from siblings like 'list_messages' by focusing on retrieval of a single message rather than listing multiple messages. However, it doesn't explicitly differentiate from other get_* tools like 'get_conversation' or 'get_folder' beyond the resource type.

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. It doesn't mention when this tool is appropriate (e.g., for retrieving a specific known message) versus when to use 'list_messages' (for browsing) or 'get_conversation' (for conversation context). There are no explicit exclusions or prerequisites stated.

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