Skip to main content
Glama

Set up an After Hours answering line (prepaid minutes or resolved conversations)

set_up_answering_line

Start a new answering line by returning the first-pack checkout link; the line is built only after the owner pays. Nothing is built or bought until the owner pays: this returns a Stripe checkout link for the first pack, and once it is paid the line is set up automatically and its number and forwarding codes are emailed to the account's address. Only call it after showing the owner https://odilelabs.com/terms and getting a yes (owner_confirmed_terms true). The packs and billing rules are in get_answering_line_offer; a line that already exists is read with get_answering_line and topped up with buy_line_pack (product 'line_minutes' or 'line_outcomes', matching its billing_mode), not set up twice. United States only: business_phone and owner_mobile take any common US format with the area code and are stored as E.164, and Canadian area codes are refused. hours keys are day names (Monday, monday or mon); a day left out is closed, and omitting hours means Monday to Friday, 9 to 5. Messages reach the owner by email and the owner console; texts stay off until the owner switches them on there. Needs a signed-in connection with the lines:manage permission; limited to 3 set-ups a day per account, and rate limited. Returns { setup_id, status: 'awaiting payment', business_name, business_phone, pack, billing_mode, minutes or outcomes, price_cents, checkout_url, then }.

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": {
      "business_name": "<business_name>",
      "business_phone": "<business_phone>",
      "owner_mobile": "<owner_mobile>",
      "pack": "<pack>",
      "owner_confirmed_terms": "<owner_confirmed_terms>"
    },
    "name": "set_up_answering_line"
  }
}

Input Schema

NameRequiredDescriptionDefault
tzNoIANA time zone for opening hours. If omitted, inferred from the business phone area code when unambiguous.
cityNoThe town the business is in, e.g. "Wellington, FL". The receptionist says it when a caller asks where you are.
packYesThe first pack: min40: 40 minutes; min200: 200 minutes; out50: 50 resolved conversations; out200: 200 resolved conversations. Amounts and billing rules: get_answering_line_offer.
extraNoAnything else the receptionist should know.
hoursNoOpening hours by day name, e.g. {"Monday": {"open": "8:00 AM", "close": "5:00 PM"}, "Sunday": "closed"}. A day left out is closed. Omit entirely for Monday to Friday, 9 to 5.
countryNoOnly US for now.
servicesNoUp to 12 services, e.g. ["drain cleaning", "water heaters"].
languagesNoLanguages besides English the receptionist switches to when a caller does.
descriptionNoWhat the business does, in one line; this is what it tells callers.
owner_mobileYesThe owner's own mobile (US, with area code): their calls to the line are never charged.
business_nameYesThe business name callers should hear, e.g. "Alvarez Plumbing".
business_phoneYesThe business number callers dial today (US, with area code, any common format such as (561) 555-0123). The owner forwards it to the new line.
owner_confirmed_termsYestrue ONLY after you showed the owner https://odilelabs.com/terms and they said yes. Anything else is refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tz
      Added value: +{
      +  "description": "IANA time zone for opening hours. If omitted, inferred from the business phone area code when unambiguous.",
      +  "maxLength": 80,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With annotations already declaring non-readonly, non-destructive, non-idempotent and open-world, the description layers substantial context: nothing is built until Stripe payment clears, number and forwarding codes arrive by email, texts stay off until enabled in the owner console, and there is a lines:manage permission plus a 3-per-day-per-account limit and general rate limiting. It also enumerates the return shape.

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?

The critical behavior is front-loaded and the ordering is logical: what it does, precondition, alternatives, geography/format rules, side effects, auth and limits, return. It is dense but dense is appropriate here; the opening 'the line is built only after the owner pays' is then restated in the following sentence, which is the one expendable repetition.

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

Completeness5/5

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

A 13-parameter tool with nested hours objects and enum-constrained packs gets full treatment: formats, defaults, geographic restriction, permission requirement, rate limits, deferred side effects, and an inline description of the returned object. Nothing an agent needs to call it correctly or set owner expectations is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the parameter documentation already carries most of the load. The description still adds real meaning beyond it: US-only with E.164 normalization and Canadian area codes refused, hours keys accepting day-name variants, omitted days closed, and omitting hours defaulting to Monday–Friday 9 to 5.

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?

States a specific verb and resource — start a new answering line — and immediately qualifies it as returning a first-pack checkout link rather than building anything. It explicitly names the siblings that handle adjacent cases (get_answering_line, buy_line_pack, get_answering_line_offer), so an agent can place it without opening another 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 a hard precondition ('only call it after showing the owner https://odilelabs.com/terms and getting a yes (owner_confirmed_terms true)') and explicit exclusions: an existing line is read with get_answering_line and topped up with buy_line_pack matching its billing_mode, 'not set up twice'. Alternatives and the selection condition are spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.