Skip to main content
Glama
PhononX

Carbon Voice

by PhononX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_message

Read-only

Retrieve a single voice message by its ID from Carbon Voice, optionally expanding related conversation, creator, or labels. Use when you have a message ID to fetch full details.

Instructions

Get one message by ID, optionally expanded with related records. USE WHEN: You have a message ID. fields ADDS related data (conversation, creator, labels) — it does not narrow the response. Use response_fields to narrow. USE INSTEAD: list_messages when you do not have an ID, or need several messages — it already returns full bodies, so fetching each one again is wasted. FIRST: id comes from list_messages (field results[].id) — call it first if you don't have one. EXAMPLE: {"id":"msg-abc","fields":"creator"} RETURNS: {message: {id, transcript?, ai_summary?, audio_url?, creator_id, duration_ms, status, type, attachments?, created_at, ...}}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
fieldsNoFields (optional) - Additional fields to include in the response. Possible values: conversation, creator, labels.
languageNoLanguage (optional) - Original language will be used if not provided or not found.
response_fieldsNoDot-path allowlist to shrink the response, e.g. ["results.id","total"]. Omit for the full payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.10.0
    • addedInput schema / properties / response_fields
      Added value: +{
+  "description": "Dot-path allowlist to shrink the response, e.g. [\"results.id\",\"total\"]. Omit for the full payload.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description doesn't need to repeat safety. It adds critical behavioral detail: 'fields' ADDS data rather than narrows, and 'response_fields' narrows. It also discloses the return shape with optional fields, giving agents a clear expectation of the response beyond what annotations convey.

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 well-structured with labeled sections (USE WHEN, USE INSTEAD, FIRST, EXAMPLE, RETURNS) that front-load the purpose and usage. Each sentence adds value, from the example to the return format, without redundancy. It is longer than minimal but every line earns its place by preventing common mistakes.

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 absence of an output schema, the description provides a return shape with optional fields. It covers parameter semantics, usage workflow, and alternatives. It does not mention error handling, but for a single-message retrieval with read-only semantics, the provided information is sufficient for an agent to call it correctly. The language parameter is covered by the schema, so no gap remains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description explains the id parameter's provenance (from list_messages), clarifies that 'fields' adds related records (listing possible values), and distinguishes it from 'response_fields' with an example. It covers the parameters more richly than the schema alone, especially for 'id' which lacks a schema description, thus compensating for the 75% coverage.

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 states a specific verb and resource: 'Get one message by ID', and immediately distinguishes it from list_messages by clarifying it retrieves a single message. It also clarifies the optional expansion with 'fields', so the purpose is unambiguous and distinct from siblings.

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

Usage Guidelines5/5

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

Explicitly provides when to use ('USE WHEN: You have a message ID') and when not to use ('USE INSTEAD: list_messages when you do not have an ID, or need several messages'), including a rationale about wasted calls. It also gives a 'FIRST' instruction on obtaining the ID from list_messages, covering the typical workflow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools