Skip to main content
Glama
PhononX

Carbon Voice

by PhononX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_conversation_users

Read-only

List the people in a conversation to identify participants and collect their user IDs and profile details. Use when you need to know who is in a specific Carbon Voice conversation.

Instructions

List the people in a conversation. USE WHEN: Finding out who is in a conversation, or collecting participant user IDs. USE INSTEAD: search_users to resolve people by name or email generally — this is scoped to one conversation. FIRST: id comes from list_conversations (field results[].id) — call it first if you don't have one. EXAMPLE: {"id":"conv-abc"} RETURNS: Array of user objects with id and profile fields. NARROW: pass response_fields ["id","full_name"] unless you need more — the full payload is much larger.

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.8/5.0
Behavior4/5

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

Annotations already convey that the tool is read-only and non-destructive. The description adds useful behavioral context beyond this: it returns an array of user objects, states that the full payload is much larger, and recommends narrowing fields to avoid it.

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 capitalized micro-headings create a scannable structure, and every sentence earns its place: when to use it, what it returns, how to get the input, an example, and a performance tip. Nothing is redundant with the schema or annotations.

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 two-parameter read-only tool with no output schema, the description covers everything an agent needs: purpose, input provenance, response shape, and field-narrowing guidance. It is complete without requiring the agent to inspect siblings or infer behavior.

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?

Schema description coverage is only 50% (the `id` parameter is undocumented). The description compensates by explaining where `id` comes from (`list_conversations` field `results[].id`), giving a concrete example, and showing exactly how to use `response_fields` to shrink the response.

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 opens with a specific verb and resource: "List the people in a conversation." It also distinguishes itself from the sibling `search_users` by emphasizing that it is scoped to one conversation, making its purpose unambiguous.

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?

The USE WHEN section states the exact use cases, and USE INSTEAD names the alternative tool and the condition selecting it. The FIRST guidance even tells the agent to call `list_conversations` first and where to find `id`, which is precise routing information.

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