Skip to main content
Glama

The owner's answering lines: status, number, balance, recent calls

get_answering_line
Read-onlyIdempotent

List the signed-in owner's existing answering lines and setups awaiting payment. Use this first for line_id, status, number, billing_mode, balance, forwarding codes and the ten latest charged calls with masked caller numbers. Product packs and terms are in get_answering_line_offer; buy_line_pack tops up a line. get_line_calls and get_line_messages read its history, get_line_call_transcript reads one call, update_answering_line edits supported settings, and create_sip_address creates or retrieves SIP credentials. Paused lines report status paused and paused_at. pause_answering_line and resume_answering_line keep the prepaid balance and number. close_answering_line ends answering, keeps the unused balance recorded and reports closed_at; use the owner console for other settings and billing. Needs lines:manage; changes nothing; rate limited per account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_answering_line"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already establish readOnly/idempotent/non-destructive, and the description adds real behavioral context on top: it requires lines:manage, 'changes nothing', is 'rate limited per account', and explains state semantics (paused lines report status paused and paused_at; close keeps unused balance recorded and reports closed_at). This is meaningfully beyond the structured hints.

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?

Purpose is front-loaded in the first sentence, and the sibling tour is compressed into two dense sentences with no filler. The enumeration of related tools and state behaviors runs long and reads as a single crowded block, costing a little scannability.

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 compensates by enumerating the returned fields and the masked-caller-number behavior. It also covers auth scope, side-effect freedom, rate limiting, and paused/closed state reporting, so an agent has everything needed to call it and interpret results.

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?

The tool takes zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description instead spends its words on the returned fields (line_id, status, number, billing_mode, balance, forwarding codes, ten latest charged calls with masked caller numbers), which is useful but not parameter semantics.

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 concrete verb and resource ('List the signed-in owner's existing answering lines and setups awaiting payment') plus the scope (signed-in owner, includes pending-payment setups). It immediately distinguishes itself from get_answering_line_offer and buy_line_pack by contrasting product packs and top-ups.

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 says 'Use this first for line_id, status, number, billing_mode...', which tells the agent this is the entry point for discovery. It then names the routing alternatives for adjacent tasks (get_line_calls, get_line_messages, get_line_call_transcript, update_answering_line, create_sip_address) and states the fallback boundary: 'use the owner console for other settings and billing.'

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.