Skip to main content
Glama
PhononX

Carbon Voice

by PhononX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_user

Read-only

Retrieve a complete Carbon Voice user profile by ID, including names, languages, voice settings, and workspace roles. Use after search_users to fetch full details for an identified user.

Instructions

Get a user's full profile by ID — names, languages, voice settings, workspace roles. USE WHEN: You already have a user ID and need complete details. USE INSTEAD: search_user / search_users to FIND someone by email, phone or name. get_current_user for the caller — this tool needs an explicit ID and will not default to you. FIRST: id comes from search_users (field id) — call it first if you don't have one. EXAMPLE: {"id":"user-abc"} RETURNS: {id, first_name, last_name?, languages, voice_gender, workspace_ids, workspace_roles, user_type, created_at, ...}. NARROW: pass response_fields ["id","first_name","last_name","workspace_ids"] 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 declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: the tool requires an explicit ID and will not default to the caller, the full payload is much larger, and response_fields can shrink it. These details go beyond the annotations and help an agent manage expectations about output size and ID requirements.

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?

Although longer than two sentences, every line earns its place. The description uses scannable headers (USE WHEN, USE INSTEAD, FIRST, EXAMPLE, RETURNS, NARROW) and front-loads the core purpose. No filler or redundant content appears, and the structured format makes 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.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description provides a return shape ('{id, first_name, last_name?, languages, voice_gender, workspace_ids, workspace_roles, user_type, created_at, ...}') and explains how to narrow it. It also covers the required parameter's provenance and an example. For a read-only get tool, this is enough for an agent to invoke it correctly and interpret results without needing additional documentation.

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 coverage is only 50% (the id property has no description), and the description fully compensates. It explains that id comes from search_users' id field, gives a concrete example ('user-abc'), and interprets response_fields as a 'Dot-path allowlist to shrink the response' with examples. Both parameters gain semantic meaning beyond the raw schema.

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 'Get a user's full profile by ID' and enumerates the fields covered ('names, languages, voice settings, workspace roles'), which clearly identifies the verb, resource, and scope. It also names its siblings explicitly under 'USE INSTEAD', distinguishing itself from search_user/search_users and get_current_user, so an agent can select it correctly without opening the schema.

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', 'USE INSTEAD', and 'FIRST' sections provide explicit conditions for use, alternatives to prefer, and the required precursor call to search_users. It even advises on narrow response fields with 'NARROW', giving concrete guidance on efficient invocation. This is exemplary when-to-use vs when-not-to-use guidance.

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