Skip to main content
Glama

Get the AI phone-line offer

get_ai_line_offer
Read-only

Get MeiSIM's current AI phone line offer: monthly price per number for texts or texts plus SIP voice, term minimum, what a US line includes, delivery time, payment methods and volume pricing.

Instructions

MeiSIM's current offer for real US phone lines used by AI agents: the monthly price per number for texts, and for texts plus voice over SIP; the first-term minimum; what a line includes (a real US mobile number on a national carrier, inbound texts to a webhook or over the API, voice over SIP with the number as caller ID, one call at a time, outbound calls to US numbers only); delivery time; payment methods; the lower price per line for more lines and who to write to from 1,000 lines; and links to apply and to the API docs. For people building voice agents, phone assistants, companion apps or SMS customer service who ask what a line costs, what it includes or how to get one. Takes no input. Read-only: it cannot open an account or order a line.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
monthlyYes
productYes
currencyYes
deliveryYes
docs_urlYes
includesYes
apply_urlYes
term_noteYes
min_monthsYes
price_ladderNo
how_to_get_oneYes
volume_contactYes
volume_pricingYes
payment_methodsYes
price_ladder_applies_toNo
usage_billed_separatelyYes
price_ladder_ask_from_linesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.5

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description still adds useful behavioral framing beyond them: 'Takes no input' and 'it cannot open an account or order a line', which tells the agent the call has no side effects and must be paired with buy_numbers/purchase to actually obtain a line. It omits any note on response freshness, caching or rate limits for a live pricing lookup.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is mostly earned, but it is delivered as one very long sentence with a deeply nested parenthetical catalog of line capabilities, which makes it hard to scan. Front-loading the offer subject is good, yet bullet points or shorter clauses would carry the same information with less parsing cost.

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 zero-parameter, read-only lookup with a full output schema and clear annotations, the description supplies everything an agent needs: what the offer covers, who it is for, that it takes no input, and that it cannot transact. The return-value detail is arguably redundant with the output schema but does not create confusion.

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?

This tool has zero parameters, so the baseline is 4. The description reinforces the schema explicitly with 'Takes no input', leaving no ambiguity about argument passing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource — MeiSIM's current offer for real US phone lines for AI agents — and enumerates exactly what the offer covers (per-number monthly price, first-term minimum, line capabilities, delivery time, payment methods, volume discounts, apply/docs links). That is far beyond a restatement of the name. It stops short of a 5 because it never distinguishes itself from the overlapping sibling get_number_pricing or get_quote, leaving the agent to guess which pricing-style tool to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The audience and triggering questions are explicit: builders of voice agents, phone assistants, companion apps or SMS customer service asking what a line costs, what it includes, or how to get one. That gives clear use context. However, it offers no when-not-to-use guidance and no explicit routing to alternatives such as get_number_pricing or get_quote, which is exactly where an agent could mis-select.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.