Skip to main content
Glama
PhononX

Carbon Voice

by PhononX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_conversation

Read-only

Retrieve a single conversation by its ID to get its description, visibility, owner, and workspace details. Use when you need conversation metadata, not messages or participants.

Instructions

Get one conversation by ID, with full metadata. USE WHEN: You have a conversation_id and need its description, visibility, owner or workspace name. USE INSTEAD: get_conversation_users for the participant list. list_messages with conversation_id for its messages — this returns neither. FIRST: id comes from list_conversations (field results[].id) — call it first if you don't have one. EXAMPLE: {"id":"conv-abc"} RETURNS: {id, name, description?, link, workspace_id, workspace_name, owner_id, type, visibility, ...}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
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

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint, and the description adds what the response contains and explicitly states it returns neither participant lists nor messages. It also sketches the return shape; a small gap is that it doesn't mention response_fields behavior, but the schema covers that.

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?

Seven short labeled sections each add distinct value: operation, trigger, alternatives, id source, example, return shape. No filler, and the key purpose is front-loaded.

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?

For a single-object read tool, everything needed to call it correctly is present: when, alternatives, id provenance, example JSON, return shape, and annotations for safety. The output schema is absent, but the RETURNS field compensates, and the optional response_fields parameter is documented in the input schema.

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?

id is just a string in the schema; the description adds its meaning (conversation_id), its provenance (list_conversations results[].id), and an example. response_fields is already described in the schema, so the description does not need to repeat it; with 50% schema coverage this is adequate compensation.

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?

Opening line names the exact operation: get one conversation by ID, and states the payload category (full metadata). The USE INSTEAD section explicitly contrasts with get_conversation_users and list_messages, so an agent can distinguish it from the nearest 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?

USE WHEN gives a concrete trigger condition (having a conversation_id and needing description, visibility, owner, workspace name). USE INSTEAD routes to the right sibling for participants/messages, and FIRST tells where the id comes from, making the decision and call sequence explicit.

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