Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
UHURA_DAILY_CALLSNoPer person: UHURA_DAILY_CALLS calls per 24 hours.
ELEVENLABS_API_KEYNoYour ElevenLabs API key, added to .env.
UHURA_RETENTION_DAYSNoCalls and transcripts are deleted after UHURA_RETENTION_DAYS.
UHURA_MONTHLY_MINUTESNoPer person: UHURA_MONTHLY_MINUTES per 30 days. A call is only dialled if the minutes left cover the longest call the agent will make (20 minutes); calls still running count at that length until their result arrives.
UHURA_DAILY_REHEARSALSNoPer person: UHURA_DAILY_REHEARSALS rehearsals per 24 hours, each closed after 10 minutes.
UHURA_ALLOWED_COUNTRIESNoOnly countries in UHURA_ALLOWED_COUNTRIES can be called.

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
draft_callA

Prepare a call without dialling. Returns the call id, the normalised number, the fixed opening line, the voicemail message and the full briefing the voice agent will receive. voicemail is what to say if a mailbox answers; a fixed AI introduction is spoken before it. Without it the agent hangs up on voicemail. topic is a short phrase completing "Es geht um …" / "It is about …" (e.g. "eine Reiseanfrage"); the agent says it in its fixed re-introduction to the first person it reaches after a phone menu or queue. No full stops or question marks. progress switches the agent's progress reports ('progress' events) on or off for this call; by default the service decides.

confirm_callA

Dial a drafted call. Only use after the user approved this specific draft.

wait_for_eventA

Wait up to timeout seconds for new events on a call (questions from the agent, 'progress' reports with stage and note, call ended). Pass the highest seq seen so far as after. Returns an empty list if nothing happened; call again until status is 'done' or 'failed'.

answerC

Answer a question the voice agent asked mid-call. question_id is the event's seq.

send_instructionA

Queue a follow-up instruction for a running call. It reaches the agent with its next tool call, at the latest just before it hangs up, so delivery is not immediate.

get_callB

Status, duration, transcript and cost of a call. cost (once the call has ended) has the ElevenLabs credits charged, the billed minutes after the silence discount, and ElevenLabs' dollar prices for the voice platform and the language model.

list_callsC

The user's recent calls, newest first.

rehearse_callA

Start a rehearsal of a drafted call: the real agent with the real briefing, in text, with nobody being called. Read what the agent says with wait_for_event, passing the returned events_after as after ('agent_said' events), and reply as the person being called with rehearse_say. Questions and instructions work as in a real call.

rehearse_sayC

Say something to the agent in a running rehearsal, as the person being called.

end_rehearsalC

End a rehearsal. The draft stays unchanged and can still be confirmed.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 10 tools

Disambiguation4/5

Most tools have clearly distinct roles: draft_call prepares, confirm_call dials, rehearse_call/rehearse_say/end_rehearsal form a coherent rehearsal group, and get_call/list_calls are reads. Minor overlap exists between answer (real-call question), send_instruction (real-call follow-up), and rehearse_say (rehearsal reply), but descriptions clarify the boundaries.

Naming Consistency4/5

Most names follow a predictable verb_noun pattern (draft_call, confirm_call, get_call, list_calls, send_instruction, rehearse_call, rehearse_say, end_rehearsal). The bare verb 'answer' and the noun-less 'wait_for_event' are minor deviations from the dominant convention.

Tool Count5/5

Ten tools is well-scoped for a voice-call agent covering drafting, dialing, live interaction, and rehearsal. Each tool earns its place with no obvious redundancy.

Completeness4/5

The lifecycle is well covered: draft, confirm, event-waiting, answering, instructing, and inspecting calls, plus a full rehearsal loop. Gaps are minor, such as no way to edit or cancel a draft, but core workflows are complete.

Maintenance

ActivityMaintained
ResponsivenessNo issues