Skip to main content
Glama

Close your prepaid answering line

close_answering_line
DestructiveIdempotent

End answering on a prepaid phone line you own. This is permanent through these controls: ask hello@odilelabs.com about reopening or the unused balance, which stays recorded without a charge, refund or forfeiture. Use line_id and the phone number from get_answering_line, then require the owner’s approval, confirm: true and its last four digits. The existing carrier close operation redirects the number to a no-longer-in-service message, clears its fallback and SMS URLs and closes its SIP address; the number is kept, never released. Calls still reaching this Worker hear “This line is closed.” on carrier routes and cannot start AI or use balance. One owner email is queued with the surface and time; no text is sent. Already closed returns already; setting-up, agency and subscription lines are refused with their management path. SIP-only lines without a phone number need support. Requires lines:manage; the same lease, fresh ownership check and account/line rate limits as pause_answering_line. Returns status, closed_at, balance_kept, already, email_queued and any warning.

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>",
      "confirm": "<confirm>",
      "last4": "<last4>"
    },
    "name": "close_answering_line"
  }
}

Input Schema

NameRequiredDescriptionDefault
last4YesThe last four digits of this answering line’s phone number, not the owner’s mobile.
confirmYesThe owner explicitly approved permanently ending answering and keeping the unused balance recorded.
line_idYesAn owned line_id from get_answering_line.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructive/idempotent/openWorld, and the description adds substantial context: permanence, carrier redirect to out-of-service, retained balance with no refund, queued owner email, what callers hear, and rate limits. It largely repeats the no-refund/balance point but overall adds rich behavioral detail beyond annotations.

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-loads the action and keeps everything information-dense, though the semicolon-chained sentences are heavy and a couple of points (balance/no-refund) are stated twice.

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 destructive, no-output-schema tool, it covers preconditions, effects, return fields, and failure modes comprehensively, leaving little an agent needs unanswered.

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 100% and covers all three params including last4 semantics and the confirm const. Description reinforces the approval/confirm/last4 flow but adds little meaning beyond the schema beyond framing it as a procedural requirement.

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 ('End answering on a prepaid phone line you own') with explicit scope (prepaid, owned). Clearly a permanent close, distinguishable from pause/resume siblings referenced elsewhere in the text.

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?

Specifies prerequisites (line_id and phone number from get_answering_line), the approval requirement, and refusal cases (already closed, setting-up/agency/subscription lines with management path). It also points to pause_answering_line as the closest analog and notes SIP-only lines need support.

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.