Skip to main content
Glama

Pause your prepaid answering line

pause_answering_line
Idempotent

Pause new incoming calls 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 paused 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": "pause_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.8/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: caller hears a fixed announcement and the call terminates with no AI, usage charges or owner alerts; missed calls appear as paused in history; direct SIP is rejected at personalization; STOP/START/HELP still function; balance and number are retained with no expiry. It also discloses the required scope (lines:manage), rate limiting, and the refusal/no-op semantics that make the idempotentHint concrete.

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 constraint (what gets paused, which line_id to use) is front-loaded in the first sentence, and each subsequent clause carries distinct information. However, the latter half becomes a dense semicolon-chained list of facts, which is harder to scan than it needs to be.

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?

There is no output schema, and the description preemptively enumerates the return fields (line_id, status, paused_at, already, message). Combined with permission, rate-limit, refund/balance, and caller-experience disclosures, nothing an agent needs to invoke or interpret this tool 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% and already documents line_id as an owned prepaid line from get_answering_line, so the description is largely restating. It does add value by enumerating which line_id states are refused (setting-up, closed, agency, subscription), telling the agent something about valid parameter values that the schema does not.

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?

Names a specific verb and resource: 'Pause new incoming calls and AI text replies on one prepaid line you own.' It also contrasts with the sibling close_answering_line, so an agent can distinguish ending a line from merely pausing it.

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?

Explicitly states the prerequisite (line_id from get_answering_line), the when-not cases (setting-up, closed, agency and subscription lines are refused; already-paused is a no-op), and names the alternative close_answering_line for permanent ending. The only mild gap is that resume_answering_line is never named as the un-pause path, but the intent is still inferable.

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.