crazytel
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CRAZYTEL_API_KEY | Yes | API key for Crazytel, sent as the x-crazytel-api-key header. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_balanceA | Get account balance (account_code, balance). |
| list_didsA | List account phone numbers / DIDs. Optional filters: did_number, country, state, city, number_type. |
| get_didB | Get details for one DID / phone number. |
| update_didC | Update DID configuration (description, primary/backup route and destination, etc.). |
| delete_didC | Delete / release a DID from the account. |
| list_available_numbersB | List available DIDs for purchase. Filters: country (default AU), state, city, number_type. |
| list_citiesA | List cities with available numbers for a state / region. |
| list_destinationsA | List routing destinations available when configuring a DID. |
| list_did_addressesA | List addresses usable when purchasing a DID. |
| list_ownersA | List person/owner records usable when purchasing a DID. |
| purchase_didC | Purchase an available DID. Requires did_number, address_id, person_id, primary_route, primary_destination. |
| list_sip_trunksA | List SIP trunks. Optional filters: username, id. |
| create_sip_trunkB | Create a SIP trunk. Requires password and caller_id_number. |
| update_sip_trunkC | Update a SIP trunk by trunk_id. |
| delete_sip_trunkC | Delete a SIP trunk by trunk_id. |
| list_verified_caller_idsA | List verified caller IDs (CLI) on the account. |
| send_smsA | Send one SMS immediately via POST /api/v2/sms/send. Requires from, to, text. Optional opt_out_list UUID and Idempotency-Key. |
| bulk_send_smsA | Bulk-send one SMS body to many recipients via POST /api/v2/sms/bulk-send. Provide from + text and either to[] or list_uuid. Sync ≤500; async 501–50k returns job_uuid. |
| get_bulk_send_jobC | Get async bulk-send admit job progress by job_uuid. |
| schedule_smsA | Schedule a single or bulk SMS via POST /api/v2/sms/schedule-send. Requires from, text, send_at, and either to or list_uuid. Cap 500 recipients. |
| list_sms_didsB | List SMS-capable DID overview from SMS Center stats. |
| list_conversationsB | List conversation threads for an SMS DID. Optional unread_only, cursor, limit. |
| get_conversationA | Read one conversation thread between a DID and counterparty. |
| list_messagesB | List SMS messages for a DID. Optional from, to, direction, status, cursor, limit. |
| get_messageB | Get SMS message detail by UUID. |
| list_contactsA | List SMS Center address-book contacts. Optional search, limit, offset. |
| create_contactB | Create an SMS Center contact. Requires phone_number; optional display_name, first_name, last_name. |
| update_contactB | Update (replace) an SMS Center contact by contact_id. |
| delete_contactC | Delete an SMS Center contact. |
| list_contact_listsA | List reusable SMS contact lists (bulk/schedule audiences). |
| create_contact_listB | Create an SMS contact list. Common fields: name, optional description and active. |
| update_contact_listA | Update SMS contact list metadata (name, description, active). Does not change members. |
| delete_contact_listA | Delete an SMS contact list (does not delete historical SMS activity). |
| add_contacts_to_listA | Add contacts to a contact list (up to 5000 per call). Body: contacts[] with phone_number each. |
| list_opt_out_listsA | List SMS opt-out / suppression lists. |
| create_opt_out_listB | Create an SMS opt-out list. OpenAPI body is loosely documented; common fields include name/slug and optional default/active flags. |
| list_opt_out_entriesC | List entries on an opt-out list. Optional status, phone, limit, offset. |
| create_opt_out_entryB | Manually suppress a recipient on an opt-out list. Requires phone. |
| check_opt_outA | Check whether a phone number is currently opted out / suppressed. Optional list_uuid scope. |
| get_sms_stats_liveB | Live SMS operational snapshot (queues / in-flight), not a billing report. |
| get_sms_stats_summaryC | Account SMS usage summary for a reporting window. Optional from/to (RFC 3339). |
| get_sms_stats_timeseriesC | SMS usage timeseries buckets. Optional from, to, bucket (hour|day|month). |
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 42 tools
Core CRUD areas are separated by resource (contacts, contact lists, DIDs, SIP trunks, opt-outs, SMS), and descriptions clarify boundaries. However, list_dids / list_sms_dids and list_messages / list_conversations / get_conversation overlap enough that an agent could initially confuse them.
The majority follow a clean list/get/create/update/delete_<resource> pattern with consistent resource nouns. Minor exceptions like add_contacts_to_list, check_opt_out, and bulk_send_sms break the pattern but remain readable.
42 tools is well beyond the range where an agent can easily keep the full surface in context, and many are close list/get variants (e.g., three SMS stats tools, two DID list tools). It would be more coherent split into SMS/DID/contacts sub-servers.
The core CRUD for contacts, contact lists, DIDs, and SIP trunks is covered, plus SMS send/bulk/schedule and stats. But opt-out lists/entries have create/list/check without delete/update, scheduled messages cannot be canceled, and contact lists have add but no remove member operation.