armavita-quo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QUO_API_KEY | Yes | Quo API key used for all API calls. | |
| QUO_HTTP_TIMEOUT_MS | No | request timeout in milliseconds (default: 30000). | 30000 |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_textA | Send an SMS text message from a Quo phone number to a recipient. Use E.164 format for phone numbers (e.g. +18325551234). The 'from' field can be a phone number ID (PN...) or E.164 number. |
| list_messagesA | List messages for a specific phone number and conversation participant. Returns messages in chronological order with pagination. |
| get_messageC | Get a specific message by its ID. |
| list_conversationsB | List conversations, optionally filtered by phone number(s), user, or date range. Ordered by most recent activity. |
| create_contactC | Create a new contact in the Quo workspace. |
| list_contactsB | List contacts in the Quo workspace with optional filtering. |
| get_contactB | Get a specific contact by ID. |
| update_contactC | Update an existing contact by ID. |
| delete_contactA | Delete a contact by ID. THIS IS DESTRUCTIVE — use with caution. |
| list_callsC | List calls for a specific phone number and participant. |
| get_callA | Get details of a specific call by ID, including duration, status, direction. |
| get_call_recordingsC | Get recordings for a specific call. |
| get_call_summaryB | Get an AI-generated summary of a call (Business/Scale plans only). |
| get_call_transcriptionB | Get the transcription of a call (Business/Scale plans only). |
| get_voicemailC | Get the voicemail for a call. |
| list_phone_numbersB | List all phone numbers in the Quo workspace, with their users and settings. |
| get_phone_numberC | Get details of a specific phone number by ID, including users, restrictions, and forwarding settings. |
| list_usersB | List all users in the Quo workspace. |
| get_userB | Get a specific user by ID, including their email, name, role, and picture. |
| get_contact_custom_fieldsA | List all custom contact fields defined in the workspace (name, key, type). Useful for understanding what custom data is tracked on contacts. |
| list_webhooksB | List all configured webhooks. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 21 tools
Most tools have distinct purposes targeting specific resources like contacts, calls, messages, phone numbers, users, and webhooks, with clear action distinctions (e.g., create_contact vs. update_contact). However, some potential overlap exists between list_calls and list_conversations, as calls might be part of conversations, which could cause minor confusion for agents.
Tool names follow a highly consistent verb_noun pattern throughout, such as create_contact, list_calls, get_user, and send_text. All tools use snake_case with clear verbs (create, delete, get, list, update, send), making them predictable and easy to understand.
With 21 tools, the count is slightly high but reasonable for a comprehensive CRM/communication platform like Quo, covering contacts, calls, messages, phone numbers, users, and webhooks. It feels a bit heavy but not excessive, as each tool serves a specific function in the domain.
The tool set provides complete CRUD/lifecycle coverage for the domain, including create, get, list, update, and delete operations for contacts, calls, messages, phone numbers, users, and webhooks. There are no obvious gaps; agents can perform core workflows like managing contacts, handling calls, and sending messages without dead ends.