Skip to main content
Glama
Sign In
CTM VoiceAI MCP

CTM VoiceAI MCP

by CTMJSON
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Get VoiceAI Agents And Instructions

ctm_voiceai_get_voice_bots
Read-only

Retrieve an account's VoiceAI agents and their current instructions, optionally filtered by agent ID or name, to compare them against call transcripts.

Instructions

Step 2 of the review flow: returns the account's VoiceAI agents and their full current instructions. Optionally filter to one agent by id or name substring. The assistant compares these instructions against the transcripts from ctm_voiceai_get_calls.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account_id": "<account_id>"
    },
    "name": "ctm_voiceai_get_voice_bots"
  }
}

Input Schema

NameRequiredDescriptionDefault
voice_botNoOptional agent id or name substring. Default: every agent that has instructions.
account_idYesCTM sub-account id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

readOnlyHint=true already establishes the safe-read profile, so the bar is lower. The description adds meaningful context beyond the annotation: it discloses the return content ('full current instructions'), states the optional single-agent filter, and explains the intended comparison workflow with get_calls. It does not, however, describe pagination, empty-result behavior, or auth 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?

Three tightly written sentences, front-loaded with the step and purpose, then the filter, then the workflow linkage. No filler and every sentence carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

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

With readOnlyHint, full schema coverage, and only two simple parameters, the description covers purpose, filtering, and return content adequately. Minor gaps remain around behavior with no matching agents and any auth/account-scoping prerequisites, but nothing essential to correct invocation is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description largely restates what the schema already states about voice_bot ('Optional agent id or name substring') without adding format or matching-rule detail, so it earns no premium over the 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?

States a specific verb and resource ('returns the account's VoiceAI agents and their full current instructions') and positions itself within a workflow ('Step 2 of the review flow'). It distinguishes itself from siblings by explicitly naming ctm_voiceai_get_calls as the complementary tool, so an agent can tell them apart without opening either schema.

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

Usage Guidelines4/5

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

Gives clear context for when to use it ('Step 2 of the review flow') and names the related tool (ctm_voiceai_get_calls) whose output it is compared against. It lacks explicit when-not-to-use guidance or filtering conditions (e.g., when to omit the voice_bot filter), so it falls short of a full 5.

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