Skip to main content
Glama
Smitline: AI Phone Calls & Meetings

Smitline: AI Phone Calls & Meetings

Start a phone call or join a meeting

start_call

Place a phone call, join a Zoom, Teams or Meet meeting, or open a new meeting room so an AI voice agent can handle the conversation from your brief and return a structured outcome.

Instructions

Place a phone call, join a video meeting, or start a new meeting room 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 the facts the call needs as context (summary, facts, and long details) so the assistant can answer questions like someone who knows the story, and set canDo whenever you could help the people on the call, at least by answering questions about the user's work. 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 at once. Then follow the call in the same turn: call wait_for_call again and again until its status is completed, failed, or canceled, because once your turn ends nothing from the call reaches you. next, the result's first field, says what to do now. If your app asks the user before each tool call, suggest once, as you start the first call, that they set wait_for_call, get_call and list_calls, and the two tools you use during a call (send_call_instruction, reply_to_call_request), to "Always allow" so you can follow and help a call without a click each time; never suggest it for start_call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "channel": "<channel>",
      "objective": "<objective>"
    },
    "name": "start_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoE.164 phone number such as +14155550142; the meeting invite URL (Zoom, Teams, Google Meet or Daily; joining by link can take a minute or two, while a hosted service starts a machine for the meeting); "new" for a meeting Smitline starts itself, a room people join from a link in any browser with no account, ready in seconds: the call then carries the room's link as to, for you to send them; or, to join a meeting by phone, its dial-in number, also as a one-tap number such as +14388097799,,85951289482#,,,,*123456# (see dialIn). Omit only for a rehearsal, which rings the user's own phone, or a meeting whose dialIn has the number. For a Google Meet link, add dialIn too when the invitation has a phone number.
taskNoThe job several calls serve, such as getting quotes from ten roofers. Use the same id for each call in it.
toneNoHow to come across, such as "casual, he is a close friend". Defaults to matching the relationship.
canDoNoWhat you will do for the people on the call when they ask, such as "look things up in the repo and edit the docs". Set it whenever you could help them, at least to answer questions about the user's work. With it, the voice passes you their requests within it and any question it cannot answer itself (live.requests in wait_for_call), and you answer each with reply_to_call_request; it declines other tasks. Without it nothing they ask reaches you: the voice can only say the user will follow up. Name only what you can do and the user would approve.
voiceNoGPT-Live voice for this call only (see list_voices). Leave it out to use the user's default voice for phone calls or for meetings.
dialInNoMeetings: join by phone. Pass the meeting's dial-in details whenever the user has them, or just paste the invitation text as invite: Smitline reads the number, the meeting ID and the passcode from it. Smitline dials in, the phone keys in the ID and passcode, and it takes part by audio, saying out loud that it is an AI. With a link in to, it joins by link and dials in if the platform turns it away (or first, where this service joins that platform by phone); with no link it always dials in. For Google Meet, pass it whenever the invitation has a Join by phone number: Google often turns guest bots away, and Smitline then joins by phone by itself. Zoom's own dial-in numbers can be dialed any time; any other number keeps the calling hours and call limits of a phone call.
notifyNo
recordNoPhone only: record this call. Smitline keeps the recording with the call, each side on its own channel, and the assistant tells the other person the call is recorded. Only when the user asks for a recording.
channelYesphone to place a call; meeting to join a Zoom, Teams, Google Meet or Daily meeting, by link or by phone, or to start a new meeting room (to "new")
contactNoWho is being called, when the user's profile does not already know this number.
contextNoThe facts the call needs that the other party may ask about. Text, or an object: summary (a few sentences), facts, decisions, openQuestions, and details (long reference material). The voice starts with a short version and looks details up when asked; it never recites them.
languageNoLanguage tag such as en or es
carryFromNoStart with short notes from earlier calls (at most 10). task: earlier calls in this brief's task; contact: earlier calls to the same number (phone only), or false to skip what the user switched on for that contact; calls: these call ids. Only carry what this call needs: the assistant may mention it to the other party, so do not carry one business's details to another unless the objective calls for it.
objectiveYesWhat the call must achieve, in one or two sentences
questionsNoWhat to find out on the call. The result answers each one.
rehearsalNoPhone only: practice a call to someone else on the user's own phone first, with the user playing that person. Not for calling the user themselves: when they say "call me", place a normal call to their number, without rehearsal.
afterHoursNoPhone calls, and meetings with dialIn: call even though it is outside calling hours (8 AM to 9 PM) where the number rings. Set only when the user confirms the person expects a call now, or for a meeting that it is on now and the number is its own.
forRequestNoWhen this call does what someone on another call asked (such as phoning Smith because a meeting asked you to): that call's id and the request's id. This call then reports to the request by itself: ringing, picked up, and the outcome or why it failed, so the people who asked hear how it went even while you are busy. You can still reply yourself. If they cancel the request, the call ends: at once if no person has spoken on it yet, otherwise after a short goodbye.
maxMinutesNoPhone calls: at most 60 (default 10). Meetings: at most 240 (default 120).
mayAgreeToNoWhat the assistant may agree to without checking back, such as acceptable times or prices
onBehalfOfNoThe person the call is for, normally the user's own name, spoken in the opening: Hi, I'm calling on behalf of NAME about... I'm NAME's AI assistant. Never an AI, model, or app name such as ChatGPT or Claude. Defaults to the name given at setup; a hosted service may set it to the account holder.
phoneMenusNoPhone only: let the assistant press keys in an automated phone menu ("press 2 for billing", "enter your account number") for a call to a business, such as a bank, utility or airline. Off by default; turn it on only when the call needs it, because menus make calls longer and cost more. The assistant keys in menu choices and numbers the brief gives for this call, never card numbers, PINs or passwords.
mustNotShareNoInformation the assistant must never share
successCriteriaNoHow to tell the call succeeded

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.3.12
    • changedInput schema / properties / afterHours / description
      Previous value: -"Phone only: call even though it is outside calling hours (8 AM to 9 PM) where the person is. Set only when the user confirms the person expects a call now."New value: +"Phone calls, and meetings with dialIn: call even though it is outside calling hours (8 AM to 9 PM) where the number rings. Set only when the user confirms the person expects a call now, or for a meeting that it is on now and the number is its own."
    • changedInput schema / properties / canDo / description
      Previous value: -"What you will do for the people on the call when they ask, such as \"look things up in the repo and edit the docs\". With it, the voice passes their requests to you (live.requests in wait_for_call) and you answer with reply_to_call_request; it also passes on any question it cannot answer itself, and declines other tasks. Omit it and nobody can ask you for anything. Name only what you can do and the user would approve."New value: +"What you will do for the people on the call when they ask, such as \"look things up in the repo and edit the docs\". Set it whenever you could help them, at least to answer questions about the user's work. With it, the voice passes you their requests within it and any question it cannot answer itself (live.requests in wait_for_call), and you answer each with reply_to_call_request; it declines other tasks. Without it nothing they ask reaches you: the voice can only say the user will follow up. Name only what you can do and the user would approve."
    • changedInput schema / properties / channel / description
      Previous value: -"phone to place a call; meeting to join Zoom, Teams, or Google Meet"New value: +"phone to place a call; meeting to join a Zoom, Teams, Google Meet or Daily meeting, by link or by phone, or to start a new meeting room (to \"new\")"
    • changedInput schema / properties / context / description
      Previous value: -"What you and the user have been working on that the other party may ask about. Text, or an object: summary (a few sentences), facts, decisions, openQuestions, and details (long reference material). The voice starts with a short version and looks details up when asked; it never recites them."New value: +"The facts the call needs that the other party may ask about. Text, or an object: summary (a few sentences), facts, decisions, openQuestions, and details (long reference material). The voice starts with a short version and looks details up when asked; it never recites them."
    • addedInput schema / properties / dialIn
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Meetings: join by phone. Pass the meeting's dial-in details whenever the user has them, or just paste the invitation text as invite: Smitline reads the number, the meeting ID and the passcode from it. Smitline dials in, the phone keys in the ID and passcode, and it takes part by audio, saying out loud that it is an AI. With a link in to, it joins by link and dials in if the platform turns it away (or first, where this service joins that platform by phone); with no link it always dials in. For Google Meet, pass it whenever the invitation has a Join by phone number: Google often turns guest bots away, and Smitline then joins by phone by itself. Zoom's own dial-in numbers can be dialed any time; any other number keeps the calling hours and call limits of a phone call.",
      +  "properties": {
      +    "invite": {
      +      "description": "The meeting invitation, as pasted: its one-tap lines, dial-in numbers, meeting ID or PIN, and passcode",
      +      "maxLength": 12000,
      +      "type": "string"
      +    },
      +    "keys": {
      +      "description": "Rarely needed: the keys to press once the call is answered, as in a one-tap number, a comma for each 2-second pause. Defaults to the platform's own timing.",
      +      "pattern": "^[0-9*#,]{1,64}$",
      +      "type": "string"
      +    },
      +    "meetingId": {
      +      "description": "What the phone line asks for: Zoom's meeting ID, Teams' phone conference ID (not the Teams meeting ID), or Google Meet's PIN",
      +      "type": "string"
      +    },
      +    "number": {
      +      "description": "The meeting's dial-in number in E.164 form, such as +14388097799",
      +      "type": "string"
      +    },
      +    "passcode": {
      +      "description": "Zoom's numeric phone passcode, printed with the dial-in numbers (not the web passcode). Teams and Meet dial-ins have none.",
      +      "type": "string"
      +    },
      +    "platform": {
      +      "description": "Whose meeting it is, when neither to nor invite says",
      +      "enum": [
      +        "zoom",
      +        "teams",
      +        "meet"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
    • changedInput schema / properties / forRequest / description
      Previous value: -"When this call does what someone on another call asked (such as phoning Arun because a meeting asked you to): that call's id and the request's id. This call then reports to the request by itself: ringing, picked up, and the outcome or why it failed, so the people who asked hear how it went even while you are busy. You can still reply yourself. If they cancel the request, the call ends: at once if no person has spoken on it yet, otherwise after a short goodbye."New value: +"When this call does what someone on another call asked (such as phoning Smith because a meeting asked you to): that call's id and the request's id. This call then reports to the request by itself: ringing, picked up, and the outcome or why it failed, so the people who asked hear how it went even while you are busy. You can still reply yourself. If they cancel the request, the call ends: at once if no person has spoken on it yet, otherwise after a short goodbye."
    • changedInput schema / properties / onBehalfOf / description
      Previous value: -"The person the call is for, normally the user's own name, spoken in the opening: Hi, I'm calling on behalf of NAME about... Never an AI, model, or app name such as ChatGPT or Claude. Defaults to the name given at setup; a hosted service may set it to the account holder."New value: +"The person the call is for, normally the user's own name, spoken in the opening: Hi, I'm calling on behalf of NAME about... I'm NAME's AI assistant. Never an AI, model, or app name such as ChatGPT or Claude. Defaults to the name given at setup; a hosted service may set it to the account holder."
    • addedInput schema / properties / phoneMenus
      Added value: +{
      +  "description": "Phone only: let the assistant press keys in an automated phone menu (\"press 2 for billing\", \"enter your account number\") for a call to a business, such as a bank, utility or airline. Off by default; turn it on only when the call needs it, because menus make calls longer and cost more. The assistant keys in menu choices and numbers the brief gives for this call, never card numbers, PINs or passwords.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / to / description
      Previous value: -"E.164 phone number such as +14155550142; the meeting invite URL (Zoom, Teams, Google Meet or Daily); or \"new\" for a meeting Smitline starts itself, a room people join from a link in any browser with no account: the call then carries the room's link as to, for you to send them. Omit only for a rehearsal, which rings the user's own phone."New value: +"E.164 phone number such as +14155550142; the meeting invite URL (Zoom, Teams, Google Meet or Daily; joining by link can take a minute or two, while a hosted service starts a machine for the meeting); \"new\" for a meeting Smitline starts itself, a room people join from a link in any browser with no account, ready in seconds: the call then carries the room's link as to, for you to send them; or, to join a meeting by phone, its dial-in number, also as a one-tap number such as +14388097799,,85951289482#,,,,*123456# (see dialIn). Omit only for a rehearsal, which rings the user's own phone, or a meeting whose dialIn has the number. For a Google Meet link, add dialIn too when the invitation has a phone number."
    • changedInput schema / properties / voice / description
      Previous value: -"GPT-Live voice name; see list_voices"New value: +"GPT-Live voice for this call only (see list_voices). Leave it out to use the user's default voice for phone calls or for meetings."
  2. Changed4 schema fields changedv0.3.5
    • changedInput schema / properties / canDo / description
      Previous value: -"What you will do for the people on the call when they ask, such as \"look things up in the repo and edit the docs\". With it, the voice passes their requests to you (live.requests in wait_for_call) and you answer with reply_to_call_request; it declines anything else. Omit it and nobody can ask you for anything. Name only what you can do and the user would approve."New value: +"What you will do for the people on the call when they ask, such as \"look things up in the repo and edit the docs\". With it, the voice passes their requests to you (live.requests in wait_for_call) and you answer with reply_to_call_request; it also passes on any question it cannot answer itself, and declines other tasks. Omit it and nobody can ask you for anything. Name only what you can do and the user would approve."
    • addedInput schema / properties / forRequest
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "When this call does what someone on another call asked (such as phoning Arun because a meeting asked you to): that call's id and the request's id. This call then reports to the request by itself: ringing, picked up, and the outcome or why it failed, so the people who asked hear how it went even while you are busy. You can still reply yourself. If they cancel the request, the call ends: at once if no person has spoken on it yet, otherwise after a short goodbye.",
      +  "properties": {
      +    "callId": {
      +      "description": "Call id returned by start_call, such as call-0123456789abcdef",
      +      "type": "string"
      +    },
      +    "requestId": {
      +      "pattern": "^r[1-9][0-9]{0,2}$",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "callId",
      +    "requestId"
      +  ],
      +  "type": "object"
      +}
    • changedInput schema / properties / record / description
      Previous value: -"Phone only: record this call in the user's phone account; the assistant tells the other person the call is recorded. Only when the user asks for a recording."New value: +"Phone only: record this call. Smitline keeps the recording with the call, each side on its own channel, and the assistant tells the other person the call is recorded. Only when the user asks for a recording."
    • changedInput schema / properties / to / description
      Previous value: -"E.164 phone number such as +14155550142, or the meeting invite URL. Omit only for a rehearsal, which rings the user's own phone."New value: +"E.164 phone number such as +14155550142; the meeting invite URL (Zoom, Teams, Google Meet or Daily); or \"new\" for a meeting Smitline starts itself, a room people join from a link in any browser with no account: the call then carries the room's link as to, for you to send them. Omit only for a rehearsal, which rings the user's own phone."
  3. Changed2 schema fields changedv0.3.2
    • changedInput schema / properties / onBehalfOf / description
      Previous value: -"The user's name, spoken in the opening: Hi, I'm calling on behalf of NAME about... Defaults to the name given at setup."New value: +"The person the call is for, normally the user's own name, spoken in the opening: Hi, I'm calling on behalf of NAME about... Never an AI, model, or app name such as ChatGPT or Claude. Defaults to the name given at setup; a hosted service may set it to the account holder."
    • changedInput schema / properties / rehearsal / description
      Previous value: -"Phone only: practice on the user's own phone first, with the user playing the other side"New value: +"Phone only: practice a call to someone else on the user's own phone first, with the user playing that person. Not for calling the user themselves: when they say \"call me\", place a normal call to their number, without rehearsal."
  4. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / canDo
      Added value: +{
      +  "description": "What you will do for the people on the call when they ask, such as \"look things up in the repo and edit the docs\". With it, the voice passes their requests to you (live.requests in wait_for_call) and you answer with reply_to_call_request; it declines anything else. Omit it and nobody can ask you for anything. Name only what you can do and the user would approve.",
      +  "maxLength": 500,
      +  "type": "string"
      +}
  5. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare readOnly=false, idempotent=false, openWorld=true, destructive=false. The description adds the crucial non-obvious behavior: the tool returns immediately and the call must be followed with wait_for_call in the same turn or nothing reaches the agent, plus that recording is announced to the other party and that canDo gates which requests reach the agent. It stops short of describing cost/limits or failure modes for link joins beyond a brief note.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then briefs, then follow-up protocol, so the reading order matches the agent's task order. It is a single dense block and the Always-allow suggestion runs long and is about app UX rather than the call itself, which slightly dilutes the operative content it sits between.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 24-parameter, nested-object tool with no output schema, the description covers the essential gap: the asynchronous return contract and the 'next' field that drives the next step, plus the reporting behavior of forRequest. It does not enumerate the shape of wait_for_call results or the final call result, leaving the agent to discover those from the sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 96%, so the baseline is 3 and the schema already documents nearly every field. The description adds real intent-level guidance for two fields — how to compose the brief for context and when to set canDo — but the bulk of its parameter talk restates what the schema already says (profile added automatically, dial-in handling, rehearsal eligibility).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb-plus-resource statement covering all three modes (place a phone call, join a video meeting, start a new meeting room) and names the agent ('Smitline') that executes it. An agent can distinguish this from the retrieval siblings (get_call, list_calls) without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to guidance (write a complete brief, set canDo whenever you could help, offer a rehearsal for a first call to someone new) and when-not guidance (do not rehearse when the user says 'call me'; never suggest Always-allow for start_call itself; ask the user rather than guessing). It also routes the agent to the exact follow-up siblings — wait_for_call repeatedly until status completes, then reply_to_call_request and send_call_instruction — so the multi-turn flow is spelled out rather than inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.