Skip to main content
Glama

start_call

Initiate phone calls through Voyp API to handle tasks like appointment scheduling or order processing, with real-time progress tracking available via returned URL.

Instructions

Start a new phone call via Voyp API. The API returns the call id and a URL where users can track the progress of the call

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYesPhone number to call in E.164 format
languageNoLanguage of the call. Ex: en-US, pt-PT, fr-FR
contextYesContext of the call. Ex: Order a pizza

Implementation Reference

  • Handler for the 'start_call' tool within the CallToolRequestSchema. Extracts number, context, and optional language from arguments, makes a POST request to the Voyp API /call/start endpoint, and returns the response data as JSON text content.
    } else if (request.params.name === "start_call") {
    
        // if (!isValidForecastArgs(request.params.arguments)) {
        //     throw new McpError(
        //         ErrorCode.InvalidParams,
        //         "Invalid forecast arguments"
        //     );
        // }
    
        const number = request.params.arguments?.number;
        const context = request.params.arguments?.context;
        const language = request.params.arguments?.language;
    
        try {
            const response = await this.axiosInstance.post<StartCallResponse>(API_CONFIG.ENDPOINTS.START, {
                number,
                context,
                language
            });
    
            return {
                content: [{
                    type: "text",
                    text: JSON.stringify(response.data)
                }]
            };
        } catch (error) {
            if (axios.isAxiosError(error)) {
                return {
                    content: [{
                        type: "text",
                        text: `Voyp API error: ${error.response?.data.message ?? error.message}`
                    }],
                    isError: true,
                }
            }
            throw error;
        }
  • src/index.ts:208-228 (registration)
    Registration of the 'start_call' tool in the ListToolsRequestSchema handler, including name, description, and input schema definition.
        name: "start_call",
        description: "Start a new phone call via Voyp API. The API returns the call id and a URL where users can track the progress of the call",
        inputSchema: {
            type: "object",
            properties: {
                number: {
                    type: "string",
                    description: "Phone number to call in E.164 format"
                },
                language: {
                    type: "string",
                    description: "Language of the call. Ex: en-US, pt-PT, fr-FR"
                },
                context: {
                    type: "string",
                    description: "Context of the call. Ex: Order a pizza"
                }
            },
            required: ["number", "context"]
        }
    },
  • TypeScript interface for the StartCallResponse returned by the Voyp API, used in the handler's axios POST call.
    export interface StartCallResponse {
      id?: string;
      url?: string;
      error?: string
    }
  • TypeScript interface matching the request body structure for starting a call, aligning with the tool's input schema.
    export interface StartCallRequest {
      number: string;
      context: string;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the API returns a call id and tracking URL, which adds some context about outputs. However, it fails to disclose critical traits like whether this is a mutating operation (implied by 'Start'), potential side effects (e.g., initiating a real phone call), error handling, or rate limits. For a tool with zero annotation coverage, this leaves significant gaps.

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 description is appropriately sized with two sentences that are front-loaded: the first states the purpose, and the second explains the return values. There is no wasted text, making it efficient. However, it could be slightly more structured by explicitly separating purpose from behavioral details, keeping it at 4 rather than 5.

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

Completeness2/5

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

Given the complexity of initiating a phone call (a mutating operation with real-world effects), no annotations, and no output schema, the description is incomplete. It lacks details on permissions, error cases, what the tracking URL entails, or how to handle the call id. For a tool with 3 parameters and significant behavioral implications, this is inadequate.

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%, meaning the input schema fully documents parameters like 'number', 'language', and 'context'. The description adds no additional meaning beyond what the schema provides, such as examples or usage notes for parameters. Baseline is 3 when the schema does the heavy lifting, but no extra value is added.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Start a new phone call') and resource ('via Voyp API'), with the verb 'Start' being specific. It distinguishes from siblings like 'get_call' or 'hangup_call' by indicating creation rather than retrieval or termination. However, it doesn't explicitly differentiate from all siblings (e.g., 'search_place' tools), keeping it at 4 rather than 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, such as authentication or account setup, or compare to sibling tools like 'get_call' for retrieving call details. Usage is implied by the action but lacks explicit context or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/paulotaylor/voyp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server