Skip to main content
Glama

Resume your prepaid answering line

resume_answering_line
Idempotent

Resume normal answering and AI text replies on one prepaid line you own. Use line_id from get_answering_line. While paused, callers hear "This line is not taking calls right now. Please try again later." and the call ends without AI, usage charges or owner alerts; missed callers appear as paused in call history. Direct SIP is rejected at personalization; the carrier controls its rejection announcement. STOP, START and HELP still work. The prepaid balance and number are kept: no charge, refund or expiry. Already live returns already without writing; setting-up, closed, agency and subscription lines are refused. close_answering_line ends answering and keeps the unused balance recorded. Needs lines:manage; rate limited per account and line. Returns line_id, status, paused_at, already and message.

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": {
      "line_id": "<line_id>"
    },
    "name": "resume_answering_line"
  }
}

Input Schema

NameRequiredDescriptionDefault
line_idYesAn owned prepaid line_id from get_answering_line.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes far beyond the annotations: describes the caller-facing message, that no charges or alerts occur while paused, that missed callers appear as paused in history, that direct SIP is rejected, that STOP/START/HELP still function, and that balance/number/expiry are preserved. It also states the required lines:manage scope, rate limiting, and the exact return fields — disclosing permissions and side effects the annotations cannot convey.

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 action is front-loaded and nearly every clause carries distinct information (refusals, no-op case, charges, auth, returns). It is dense and semicolon-chained, but trimming would lose genuine behavioral facts rather than padding.

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?

For a single-parameter mutation with no output schema, the description covers the action, preconditions, refusal cases, idempotent no-op behavior, cost implications, permissions, rate limits, and the return payload. Nothing an agent needs to invoke it safely is missing.

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?

Only one parameter and schema coverage is 100%, with the description of line_id already in the schema. The description repeats that it must come from get_answering_line but adds no format, constraint, or edge-case meaning beyond the structured field, so the baseline of 3 applies.

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 and resource: 'Resume normal answering and AI text replies on one prepaid line you own.' Combined with the refusal list and the contrast to close_answering_line, an agent can distinguish this from pause/close/setup siblings without opening any 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?

Names the prerequisite source of line_id (get_answering_line), lists the line states that are refused (setting-up, closed, agency, subscription), explains the no-op case for already-live lines, and points to close_answering_line for the opposite intent. When-to-use, when-not, and the alternative are all explicit.

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.