Skip to main content
Glama
Sign In

Latchbell

by com.latchbell
OverviewDiscussionsAdmin

Set phone call voice

receptionist_call_voice

Owners only (needs sign-in): Sets the speech model voice for this business's phone line (inbound and every place_phone_call), until changed again. Default is Aoede. Pass a Gemini prebuilt voice name (letters only, e.g. "Aoede", "Puck"); pass an empty string to reset to the default. place_phone_call cannot pick a different voice per call — set it here or read phone.call_voice in receptionist_service. Tone and language on a specific outbound call belong in place_phone_call's purpose; the inbound opening line belongs in front_desk greeting (update_front_desk).

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": {
      "voice": "<voice>"
    },
    "name": "receptionist_call_voice"
  }
}

Input Schema

NameRequiredDescriptionDefault
voiceYes

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?

Beyond the annotations marking this as a non-read-only, open-world, non-destructive mutation, the description discloses sign-in/owner requirements, the default voice (Aoede), persistence until changed, and that the setting applies to inbound calls and every place_phone_call. It also clarifies that place_phone_call cannot override the voice per call.

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 dense but front-loaded with the core action, permission requirement, default, and reset behavior. Every clause adds operational value, including the sibling-tool routing details, with no redundant restatement of the name or title.

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 one-parameter mutation with no output schema, the description covers the key missing pieces: permissions, persistence, default behavior, accepted value format, reset mechanics, and how to read the current value via phone.call_voice in receptionist_service. It also routes adjacent concerns to the correct sibling tools.

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 0%, so the description carries the full burden for the single voice parameter. It explains that the value should be a Gemini prebuilt voice name using letters only, provides examples such as "Aoede" and "Puck", and states that an empty string resets to the default.

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 states a specific verb and resource: it sets the speech model voice for this business's phone line, affecting inbound calls and every place_phone_call until changed. It also distinguishes this persistent setting from per-call behavior in place_phone_call and the inbound greeting in update_front_desk.

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?

It gives explicit when-to-use context: owners only, sign-in required, use a Gemini prebuilt voice name, or pass an empty string to reset. It also names where related settings belong, stating that outbound-call tone and language go in place_phone_call's purpose and the inbound opening line belongs in update_front_desk.

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

All Latchbell toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources