Skip to main content
Glama
paulotaylor

Voyp MCP Server

by paulotaylor

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
VOYP_API_KEYYesYour Voyp API key obtained from https://voyp.app/app.html

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
start_callC

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

hangup_callC

Hangup an existing call

search_placesC

Search places in a given location

search_placeC

Search place details in a given location

search_place_by_numberB

Find place name and address by phone number

get_callC

Retrieve call details

get_userB

Retrieve user profile

Prompts

Interactive templates invoked by user choice

NameDescription
start-callStart a new call
hangup callHangup an existing call

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 7 tools

Disambiguation3/5

The tools have some clear distinctions, such as get_call vs. hangup_call vs. start_call for call operations, but there is significant overlap between search_place, search_places, and search_place_by_number, which could cause confusion about which to use for location-based searches. The descriptions help clarify, but the boundaries are not perfectly distinct.

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern (e.g., get_call, get_user, hangup_call, start_call), with clear and readable naming. However, the search tools have minor deviations (search_place, search_places, search_place_by_number), which slightly disrupts the pattern but remains mostly consistent.

Tool Count5/5

With 7 tools, the count is well-scoped for a server focused on phone calls and place searches. Each tool appears to serve a specific purpose without unnecessary duplication, fitting within the typical 3-15 range for a coherent toolset.

Completeness3/5

For call operations, there is good coverage with get, start, and hangup, but missing update or list operations for calls or users could be a gap. For place searches, the tools cover various search methods, but without create or delete operations, the surface feels incomplete for a full lifecycle in the domain.

Maintenance

ActivityInactive
ResponsivenessUnresponsive