Skip to main content
Glama

Compare receptionists at a call volume

compare_at_volume
Read-onlyIdempotent

Monthly cost of every AI or virtual receptionist at a call volume and call length, lowest first, from each vendor's cheapest published plan plus overage. Quote-only vendors are listed separately. Defaults: AI receptionists, 3-minute calls. 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": {
      "calls": "<calls>"
    },
    "name": "compare_at_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoai
callsYesCalls a month (13 calls a day, the small-business average in Google CallJoy's testing, is 390)
minutes_per_callNoAverage minutes per call

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/closed-world annotations, the description discloses the pricing methodology (cheapest published plan plus overage), the treatment of quote-only vendors (listed separately), the result ordering (lowest first), and the data source and freshness date. That is exactly the behavioral context an agent needs to trust and present the numbers, and it does not conflict with the 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?

The core behavior and ordering are front-loaded in the first sentence, followed by the quote-only caveat, the defaults, and provenance. Four sentences with no filler; only the source URL and verification date add a little tail weight, though they serve as useful provenance.

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?

For a three-parameter read-only comparison with no output schema, the description covers what is computed, how it is sorted, and how edge-case vendors appear, which is enough to interpret the result. The remaining gap is the unexplained `type` enum and the absence of any hint about result fields, though the 'monthly cost ... lowest first' phrasing implies a ranked cost list.

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 67%, so the baseline is 3. The description restates the `type` and `minutes_per_call` defaults already declared in the schema but never explains the four `type` enum values (ai, virtual, platform, all) — notably 'platform', which is not self-evident — leaving the least obvious parameter undocumented in both places.

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 a specific computation ('monthly cost of every AI or virtual receptionist at a call volume and call length, lowest first') rather than restating the name. It also discloses the calculation basis (cheapest published plan plus overage) and how quote-only vendors are handled. It never names a sibling to differentiate itself from category_range or hire_vs_ai, which leaves a small ambiguity an agent must resolve from scope alone.

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?

Usage context is clear: this is the tool to call when you want a cost ranking at a specified call volume, with defaults (AI receptionists, 3-minute calls) spelled out so the agent knows it can call with only `calls`. There is no explicit when-not guidance and no mention of category_range or hire_vs_ai as alternatives, so nothing prevents a wrong sibling choice in edge cases.

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