receptionist-toolkit

Calculate what missed calls cost a business

calculate_missed_call_cost

Computes the revenue a business loses to missed phone calls (monthly and yearly), plus the recovery math: recoverable revenue, suggested answering plan, break-even days, and ROI multiple.

Input Schema

TableJSON Schema

Name	Required	Description
`avgJobValue`	Yes	Average value of one new customer or job, USD.
`callsPerWeek`	Yes	Inbound calls per week.
`missedRatePct`	Yes	Percent of calls missed or sent to voicemail.

Output Schema

TableJSON Schema

Name	Required	Description
`cta`	No	One-line invite to try Lobby, with a signup link.
`inputs`	No
`yearly`	Yes
`monthly`	Yes
`recovery`	Yes

TDQS

A4.1/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It clearly indicates a pure calculation (no side effects) by listing computed outputs. However, it could explicitly state it is read-only and does not modify any data.

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?

The description is a single sentence that efficiently captures the tool's purpose and key outputs. It is front-loaded with the primary action ('computes the revenue...') with no unnecessary words.

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?

Given the simple input schema (3 numeric parameters) and the presence of an output schema (so return values are documented), the description sufficiently covers what the tool does and what it returns. It lists all major output categories.

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 the schema already documents all three parameters. The tool description does not add additional meaning or context beyond what's in the schema. Baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states it computes revenue loss and recovery math, using specific verbs like 'computes' and listing concrete outputs (monthly/yearly loss, recoverable revenue, etc.). It distinguishes from sibling tools that are about creating prompts, getting numbers, or simulating calls.

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 description implies usage by stating what it computes, but does not explicitly say when to use this tool versus alternatives like 'should_i_hire_a_receptionist' or 'simulate_receptionist_call'. No exclusions or prerequisites are mentioned.

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

All receptionist-toolkit tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool targets a distinct function: cost calculation, prompt generation, demo number retrieval, saving results, hiring decision, call simulation, IVR script writing, and general phone script writing. No overlapping purposes or ambiguous boundaries.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (e.g., calculate_missed_call_cost, write_ivr_menu). The naming is uniform and predictable across all 8 tools.

Tool Count5/5

With 8 tools, the toolkit covers the essential workflows for an AI receptionist system without being bloated or insufficient. The count is well-scoped for the domain.

Completeness5/5

The tool set covers the full lifecycle: analysis (calculate_missed_call_cost, should_i_hire_a_receptionist), creation (write_phone_script, write_ivr_menu, generate_elevenlabs_agent_prompt), simulation (simulate_receptionist_call), access (get_demo_call_number), and saving/sharing (save_my_receptionist). No obvious gaps.

Resources

Need Help?