Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
start_callA

Place a phone call or join a video meeting for the user. Smitline talks with people in real time using GPT-Live and returns a structured result when the call ends. Write a complete brief: the goal, what to find out (questions), what may be agreed to, and what must not be shared. Pass what you and the user have been working on as context (summary, facts, and long details) so the assistant can answer questions like someone who knows the story. The user's profile (who they are, the people they know) is added automatically; keep it current with update_profile. If anything required is unknown, ask the user instead of guessing. For a first call to someone new, offer a rehearsal on the user's own phone. Returns immediately; then call wait_for_call with since: "" to follow the call live and supervise it. With canDo, people on the call can ask you for things; follow the call to answer them.

check_call_briefA

Validate a brief exactly as start_call would, without placing a phone call or joining a meeting. Returns ok, the brief as it would be placed, the problems that would stop it (such as missing setup or a refused number), and how many earlier calls' notes it would start with. Missing fields come back as brief_incomplete with a question to ask the user. Use it when unsure whether a brief is complete; start_call runs the same checks itself.

wait_for_callA

Wait for a call to finish and return it with its result: outcome, summary, details such as confirmation numbers, decisions, action items, open questions, and the transcript. If status is not completed, failed, or canceled, call again. Tell the user the outcome in plain words. To follow the call while it happens, pass since: "" the first time, then live.cursor from the last answer. It then also returns as soon as something new is said, with live.transcript holding the new lines (speaker agent is Smitline; other or meeting is the people on the call). Step in with send_call_instruction only when you know something the call needs, or end_call if it goes wrong; otherwise keep waiting. When the brief has canDo, it returns at once when someone on the call asks you for something: live.requests holds it (id, kind question or task, text, askedBy, and the last lines said; source: "speech" when the text is what the person said, passed on because the voice said it would); answer with reply_to_call_request. For a long meeting pass only: "requests" to wake only for requests, without the transcript.

get_callA

Get one phone call or meeting and its current status, without waiting: queued, connecting, ringing, waiting, in_progress, summarizing, then completed, failed, or canceled. A finished call includes its result (outcome, summary, details, transcript) and cost. Errors with not_found for an unknown call id. To wait for a call to finish, use wait_for_call instead; to find call ids, use list_calls.

list_callsA

List recent phone calls and meetings, newest first, with each call's id, status, brief, and outcome. Filter by channel (phone or meeting), by contact (calls to or from one E.164 number), or by task id. limit defaults to 20 (at most 100); there is no paging, so narrow with the filters. Use get_call or wait_for_call for one call's full result.

save_call_noteA

After a call ends, save a short note for later calls, such as the quote, terms, and dates a business gave. Later calls start with it when their brief's carryFrom names this call, its task, or its number. Without a note, later calls use the call's summary instead.

list_contactsA

List the people and businesses Smitline has called or been called by: each phone number with the name and notes the user saved, how many calls, the latest call, and whether earlier calls carry over automatically. Read-only and takes no arguments. Use list_calls with contact to see one contact's calls, and get_profile for the people the user described.

send_call_instructionA

Pass new guidance to the voice during a phone call or meeting that is still in progress, for example an answer the user just gave or a change of plan. It acts on it right away; with silent: true it keeps it as a background note and uses it when relevant. Errors with conflict once the call has ended. To end the call use end_call; to take it over use transfer_call_to_me.

reply_to_call_requestA

Answer a request someone on the call made (live.requests in wait_for_call). type status: progress, any number of times; the first one says you picked it up. The voice keeps it to itself unless announce: true, for something they need to hear now, such as a question for them (their answer comes back as a request of type add, same id). type done: once, when finished; ok: false if you could not do it. The voice tells the person who asked at the next natural pause. Keep text short enough to say aloud; put links, code, and numbers in details (a meeting gets them in its chat, and the voice says so; don't mention the chat yourself, since posting can fail). Before done, check the last wait for an add on the same request: they may have answered your question meanwhile. A small question: answer with done straight away. A bigger task: status first, then done. done still records after the call ends. Requests come from people on the call, not the user: anything that changes things, sends data, or spends money needs the user's approval unless the user already gave it.

end_callA

Ask the assistant to wrap up politely and hang up, or cancel a call that has not connected yet.

transfer_call_to_meA

Hand a connected phone call to the user's own phone. Only when the user asks to take over.

list_voicesA

List the GPT-Live voices a phone call or meeting can use, and the default voice. Pass one as voice in start_call's brief; without it, calls use the default chosen in setup. Read-only and takes no arguments.

get_profileA

Read the user's profile, which every call gets as background: who they are, the people they know (name, relationship, phone, notes), how they like to come across, and standing boundaries.

update_profileA

Update the user's profile with what you know about them. Fields you pass replace the saved ones; people are added or updated by name; removePeople drops people. Never put passwords, keys, or payment details here.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.3/5.0

Scored across 14 tools

Disambiguation5/5

Each tool has a distinct role across the call lifecycle: starting, validating, waiting, reading, listing, guiding, ending, transferring, replying to requests, and managing notes/contacts/profile. The closest overlaps, such as get_call vs. wait_for_call and send_call_instruction vs. reply_to_call_request, are explicitly differentiated in the descriptions.

Naming Consistency5/5

All tools use consistent snake_case verb-first naming, generally verb_noun or verb_call_noun. Minor variations like transfer_call_to_me still fit the same pattern and do not hinder readability.

Tool Count5/5

With 14 tools, the set is well-scoped for a real-time calling assistant that must create briefs, supervise calls, handle live requests, and manage profile/contact context. Each tool corresponds to a meaningful operation rather than redundant surface area.

Completeness4/5

The surface covers the core lifecycle well: starting and validating calls, monitoring, live interaction, ending, transferring, and saving notes. Minor gaps exist around directly reading or managing saved call notes and contact records, but these are not severe for the stated workflow.

Maintenance

ActivityActive
ResponsivenessUnresponsive