Skip to main content
Glama
PhononX

Carbon Voice

by PhononX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search_user

Read-only

Find a single Carbon Voice user by email, phone, or name. Name search matches only your contacts; use email or phone for non-contacts.

Instructions

Find a single user by email, phone or name. USE WHEN: Resolving ONE person. Supply exactly one of email, phone or name. Name search only matches your own contacts. USE INSTEAD: search_users for several people in one call — it takes arrays and saves a round trip per person. get_user when you already have the ID. EXAMPLE: {"email":"someone@example.com"} RETURNS: {id, full_name, first_name, last_name?, link, image_url?, languages?, ...}. Use id wherever another tool asks for a user ID. ERROR NOT_FOUND: Nobody matched, or a name search hit a non-contact. — Try an email or phone instead of a name; name search is limited to your contacts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoThe name of the user to search for (Only users that are part of your contacts will be returned)
emailNoEmail Address
phoneNoPhone Number

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 safety profile is covered. The description adds valuable behavioral details beyond the schema: name search only matches contacts, the exact return shape, the instruction to use id in other tools, and NOT_FOUND error semantics with recovery guidance. No contradiction with annotations.

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 organized with clear labels (USE WHEN, USE INSTEAD, EXAMPLE, RETURNS, ERROR) and front-loaded with the primary purpose. Every section serves a distinct purpose: routing, constraints, example, output format, and error handling. No redundant or filler content.

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 tool with no output schema, the description compensates by specifying the return fields and the NOT_FOUND error behavior. It covers prerequisites, parameter constraints, alternatives, output usage, and error recovery, making the tool fully callable by an agent without further inference. The annotations cover safety, and the description covers the rest.

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?

Although schema coverage is 100%, the description adds crucial semantics: 'Supply exactly one' enforces exclusivity among the three parameters, and the note that name search only matches contacts clarifies the meaning of the name parameter beyond its schema description. The example also demonstrates a valid parameter combination.

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?

States a specific verb and resource ('Find a single user by email, phone or name') and differentiates from siblings like search_users (plural) and get_user (by ID). The phrase 'Find a single user' immediately signals scope and distinguishes the tool from alternatives.

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?

Provides explicit USE WHEN conditions ('Resolving ONE person', 'Supply exactly one of email, phone or name') and USE INSTEAD alternatives with rationale (search_users for arrays, get_user when ID is known). The contact-only limitation for name search is also clearly stated, giving the agent actionable routing logic.

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