Skip to main content
Glama

Should this business hire a receptionist?

should_i_hire_a_receptionist

Evaluate your business's phone coverage and get a verdict: covered, AI front desk, or hybrid, with ROI and break-even analysis.

Instructions

Scores a business's phone coverage and returns a verdict — you're covered, get an AI front desk, or go hybrid — with the caller archetype, yearly leak, suggested plan, break-even days, and ROI.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
avgJobValueYesAverage value of one new customer or job, USD (snapped to the quiz's brackets).
callsPerWeekYesRoughly how many inbound calls per week (snapped to the quiz's brackets).
currentSetupNoWho answers today: the owner (self), voicemail (vm), staff between tasks (staff), or nobody consistently (none). Default: self.
missedRatePctYesRough percent of calls that go unanswered (snapped to the quiz's brackets).
coverageNeededNoWhen calls actually come in. Default: business-hours.
spanishCallersNoHow often Spanish-speaking customers call. Default: no.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
scoreYesPhone-coverage maturity score, 0-100.
verdictYescovered = current setup is fine; lobby = an AI front desk pays for itself; hybrid = AI + existing staff.
recoveryNo
archetypeYes
yearlyLeakYesUSD lost per year with the current setup.
Behavior3/5

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

With no annotations, the description should disclose side effects and read-only nature. It implies a calculation but doesn't explicitly state it is deterministic and non-destructive. Lacks clarity on whether it modifies state.

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?

Single sentence, well-structured, includes key outputs. No unnecessary words.

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?

Description covers purpose, verdict types, and return fields. With output schema present, it is fairly complete. Could mention it's a scoring/calculation tool but overall sufficient.

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 100%, so baseline 3. Description adds no parameter context beyond what schema provides, but schema is complete. No extra semantic guidance on parameter importance or relationships.

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 clearly states the tool scores phone coverage and returns a verdict with metrics, using specific verbs. However, it does not differentiate from sibling tools like calculate_missed_call_cost or simulate_receptionist_call.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives such as calculate_missed_call_cost or simulate_receptionist_call. Missing context on prerequisites or scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bodyegypt/lobbyvoices-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server