Skip to main content
Glama

What hiring a receptionist costs, against AI and virtual receptionists

hire_vs_ai
Read-onlyIdempotent

Monthly cost of an in-house receptionist from BLS data (OEWS median wage for SOC 43-4171, national or by state; ECEC employer benefits other than paid leave, which is already paid inside 2,080 paid hours; NCS paid leave days; JOLTS quits times a published replacement-cost share), for one full-time hire or for full cover of N hours a week, next to the cheapest AI and virtual receptionist at the same call volume. Source: ReceptionistPrices.com, prices checked November 17, 2026, https://www.receptionistprices.com/hire-vs-ai/

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": "hire_vs_ai"
  }
}

Input Schema

NameRequiredDescriptionDefault
callsNoCalls a month
stateNoTwo-letter state code, e.g. TX
hours_per_weekNoHours a week the phone must be covered; omit for one full-time hire

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses exactly what the computation includes: OEWS median wage for SOC 43-4171, ECEC employer benefits excluding paid leave (already inside 2,080 paid hours), NCS paid leave days, and JOLTS quits times a published replacement-cost share. It also names the source and the price-check date, giving the agent a clear picture of methodology and data freshness.

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 core output is front-loaded, but it is delivered as one very long sentence with stacked parentheticals and semicolons, which is hard to parse on first read. Every clause carries information, yet restructuring into a short purpose sentence plus a methodology note would cost nothing in content.

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 should signal the shape of the return; 'monthly cost ... next to the cheapest AI and virtual receptionist' implies a comparative cost result, and the methodology detail is unusually complete. It stops short of stating currency, period basis, or the exact response fields, which is the remaining gap.

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 description coverage is 100%, so calls, state, and hours_per_week are already documented, including the 'omit for one full-time hire' behavior. The description reinforces the call-volume and hours framing but adds no new syntax, units, or edge-case semantics beyond the schema.

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 the concrete output (monthly cost of an in-house receptionist) and the comparison it produces (cheapest AI and virtual receptionist at the same call volume), with the underlying data sources spelled out. It is specific enough to distinguish it from a generic vendor-pricing sibling, though it never explicitly contrasts itself with compare_at_volume or get_vendor_pricing.

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?

The use case (comparing a hire against AI/virtual options at a given call volume) is implied clearly by the wording, and the 'one full-time hire or full cover of N hours a week' clause hints at the two modes. There is no explicit when-to-use/when-not-to-use statement and no routing to siblings, so guidance is inferred rather than stated.

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