Skip to main content
Glama
Smitline: AI Phone Calls & Meetings

Smitline: AI Phone Calls & Meetings

List voices

list_voices
Read-only

Retrieve the GPT-Live voices available for calls and the user's default voices for phone calls and meetings. Use it to check which voice a call or meeting will use before updating defaults.

Instructions

List the GPT-Live voices calls can use, and the user's default voices: defaults.phone for phone calls, defaults.meeting for meetings (joined by link or by phone). A brief's voice wins over both for that call; update_profile with voices changes a default. Read-only and takes no arguments.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_voices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description's real contribution is the precedence rule - a brief's voice overrides defaults.phone and defaults.meeting for that specific call, and defaults split by join channel (link vs. phone). That resolution behavior is not derivable from any structured field.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead clause front-loads what is returned and the defaults mapping is packed into the same sentence with no filler. The trailing "Read-only and takes no arguments" partially restates the annotations and empty schema, but it is short enough that the redundancy costs little.

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 parameters, no output schema and full annotation coverage, the only real gaps would be return shape and precedence - both addressed (the voice list, the two default keys, and brief-over-default resolution). An agent has everything needed to call it and correctly interpret which voice actually applies.

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?

Parameter count is zero, so the baseline is 4; the description confirms "takes no arguments," matching the empty schema with additionalProperties=false. There is no parameter nuance left to explain.

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+resource ("List the GPT-Live voices calls can use") and immediately extends it to the user's default voices with concrete field paths (defaults.phone, defaults.meeting). It also names the mutation sibling, update_profile, so the agent can distinguish the read path from the write path without opening a 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?

It gives clear context for use - discovering selectable voices and seeing per-channel defaults - and explicitly routes changes to update_profile with voices. What it lacks is an explicit trigger statement tying the call to a downstream action (e.g., 'call this before start_call to pick a voice'), so the when-to-use is inferred rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.