Skip to main content
Glama

Price range and median for AI or virtual receptionists

category_range
Read-onlyIdempotent

The range and median monthly cost of AI receptionists or live virtual receptionists at a call volume (3-minute calls), the all-in rate per minute and the range of entry plans. Source: ReceptionistPrices.com, prices checked November 17, 2026, https://www.receptionistprices.com/ai-receptionist-cost/

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": {
      "type": "<type>"
    },
    "name": "category_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesai, or virtual (live people)
callsNoCalls a month

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 profile is covered; the description adds genuine context beyond that by naming the data source (ReceptionistPrices.com), the freshness date (November 17, 2026), and the 3-minute-call basis underlying the figures. It does not state currency or whether figures are current-month snapshots versus annualized, which keeps it from 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.

Conciseness5/5

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

A single front-loaded sentence delivers the core deliverable first and trails the provenance and URL last, with no filler or repetition. Dense but every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must describe the return payload, and it does list the metrics returned (range, median, per-minute all-in rate, entry-plan range). Remaining gaps are minor for a two-parameter, read-only pricing lookup — mainly currency and output shape.

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%, so the baseline is 3, but the description earns an extra point by clarifying that 'calls' means calls per month measured in 3-minute-call units — information the schema's 'Calls a month' does not convey. The type enum (ai vs virtual/live people) is fully documented in the schema and is not restated in detail here.

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 states the concrete subject — monthly cost range and median for AI vs live virtual receptionists at a given call volume — plus the extra outputs (all-in per-minute rate, entry-plan range). It implicitly separates itself from vendor-level tools like get_vendor_pricing by being category-level, but never names a sibling to sharpen that boundary.

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

Usage Guidelines3/5

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

Usage is only implied: the phrase 'range and median monthly cost ... at a call volume' signals this is the category-level, volume-parameterized pricing tool, so an agent can infer it is the right pick for a quick ballpark rather than per-vendor detail. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. compare_at_volume, get_vendor_pricing).

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.

Resources