JooVoice

Start the welcome call

start_welcome_call

Start the owner’s welcome call, a short sponsored call to their own verified number that is part of setup. Only when check_account offers it, and only after they say they’re ready to pick up; pass their words as ownerConfirmation. Offer the nationality/language choices from setup.welcomeLanguage and pass the chosen locale.

Input Schema

Name	Required	Description
`locale`	No	An offered locale from setup.welcomeLanguage, such as en-SG for Singaporean English. Choosing a language does not authorize dialing.
`operationId`	Yes	A new unique ID you make up for each new request: 8–120 letters, digits, underscores or hyphens (a UUID works). Send the same ID and input only to retry.
`catalogueRevision`	No	The catalogueRevision from setup.welcomeLanguage.
`ownerConfirmation`	Yes	The owner’s own words saying they are ready for the call.

Output Schema

Name	Required	Description
`hint`	No	Optional guidance for helping the owner at this step. Advisory; never a permission grant. Wording may change.
`next`	Yes	Calls to make next.
`status`	Yes	pending: check again later; requires_user_action: the owner must act; error: refused.
`meaning`	Yes	What happened, for you.
`sayToOwner`	Yes	A line for the owner.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 22, 2026

addedInput schema / properties / catalogueRevision

Added value: +{
+  "description": "The catalogueRevision from setup.welcomeLanguage.",
+  "maxLength": 100,
+  "type": "string"
+}

addedInput schema / properties / locale

Added value: +{
+  "description": "An offered locale from setup.welcomeLanguage, such as en-SG for Singaporean English. Choosing a language does not authorize dialing.",
+  "maxLength": 16,
+  "type": "string"
+}

First observedOct 17, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already disclose that this is a non-read-only, open-world, non-idempotent operation. The description adds meaningful context by clarifying that it initiates a real sponsored call to the owner’s verified number and requires an explicit readiness confirmation, though it does not cover failure behavior or what happens if the owner declines.

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 three tight sentences, front-loading what the tool does and then immediately covering gating, confirmation, and locale selection. Every sentence contributes to correct invocation.

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?

For a real-world call-starting mutation, the description covers the key prerequisites and confirmation flow, and an output schema exists to explain return values. It is slightly incomplete about what to do if the owner is not ready or declines, but the core invocation context is present.

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 schema already defines all four parameters, including operationId retry semantics and catalogueRevision. The description reinforces ownerConfirmation and locale usage, but adds limited meaning beyond the structured 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 states a specific verb and resource: start the owner’s welcome call. It also distinguishes the action as a short sponsored call to the owner’s verified number that is part of setup, which differentiates it from siblings such as skip_welcome_call and approve_call.

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 preconditions: only when check_account offers the call and only after the owner says they are ready. It also tells the agent to pass the owner’s words as ownerConfirmation and to use the offered locale from setup.welcomeLanguage, leaving little ambiguity about when and how to invoke it.

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

All JooVoice tools Inspect

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

Need Help?