Skip to main content
Glama

After Hours answering line, prepaid minutes or resolved conversations: the offer

get_answering_line_offer
Read-onlyIdempotent

Read the available answering-line packs and billing rules before choosing a purchase. Use set_up_answering_line for the first pack and a new line, or buy_line_pack to top up an existing line. This is public product information, not your own balance or status (get_answering_line); takes no arguments, changes nothing and contacts no business. Returns minute/outcome packs, billing rules, zero-balance rules, supported countries and terms_url from the same tables as checkout.

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_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety bar is low. The description still adds meaningful context beyond them: zero arguments, no contact with any business, public (not account-scoped) information, and the fact that the returned data comes 'from the same tables as checkout,' which tells the agent the prices are authoritative. It stops short of describing pagination or freshness, keeping it just under a 5.

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?

Three tight sentences, front-loaded with the purpose, then routing, then scope and return contents; every sentence carries unique information. The parenthetical and em-dash asides make it slightly dense to parse but are not wasted words.

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?

With no parameters and no output schema, the description carries the burden of explaining what comes back, and it does: minute/outcome packs, billing rules, zero-balance rules, supported countries and a terms_url. An agent has everything needed to call it and anticipate the payload.

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?

There are zero parameters, so the baseline is 4. The description confirms 'takes no arguments,' which aligns with the empty schema and prevents the agent from probing for optional filters.

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?

The description opens with a specific verb and resource: 'Read the available answering-line packs and billing rules.' It then explicitly distinguishes itself from three siblings by naming them and their distinct roles (get_answering_line for your own balance, set_up_answering_line for a first pack, buy_line_pack for 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?

It states exactly when to call this ('before choosing a purchase') and routes the agent to the correct alternative for each adjacent intent, including an explicit exclusion: 'not your own balance or status (get_answering_line).' No inference is required to pick between this and its siblings.

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.