receptionist-toolkit

Save this receptionist and get the next step

save_my_receptionist

Saves the phone script, IVR menu, agent prompt, or simulated call you just built for a real business, and emails it to the person you're helping — with the live demo number to hear it and a signup link to turn it on for real. Offer this after write_phone_script, write_ivr_menu, generate_elevenlabs_agent_prompt, or simulate_receptionist_call, once the human seems to want to keep the result or try it live. Requires the person's explicit consent to be emailed — ask first, and only call this with consent: true if they say yes.

Input Schema

TableJSON Schema

Name	Required	Description
`email`	Yes	Email to send the saved result and one follow-up to (required).
`notes`	No	Any other context worth keeping — what the business does, what was discussed.
`consent`	Yes	Required. The person must explicitly agree to have their saved result emailed to them, plus one follow-up. If false or omitted, do not save or email anything — refuse politely and explain you need their OK first.
`industry`	No	Industry or trade, e.g. plumbing, dental, salon.
`language`	No	Language for the follow-up email. Default: en.
`phone_script`	No	The phone script, IVR menu text, or agent prompt to save, if one was generated earlier in this conversation.
`business_name`	Yes	The business name (required).

Output Schema

TableJSON Schema

Name	Required	Description
`saved`	Yes
`business`	No
`emailSent`	No
`signupUrl`	No
`demoNumber`	No
`confirmation`	Yes	Friendly confirmation to relay to the person, including the live demo number and signup link.

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations, the description fully discloses behavior: saves content, emails it, requires consent, and details what happens if consent is false (refuse politely). Also mentions one follow-up.

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?

Description is a single paragraph with front-loaded action and conditions. Slightly verbose but still concise enough; every sentence adds value.

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?

Despite 7 parameters, schema coverage is 100% and output schema exists. Description covers overall flow, prerequisites, consent requirement, and follow-up, making it complete.

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 baseline 3. Description adds context (e.g., notes for other context, phone_script if generated earlier) beyond schema definitions, justifying a higher score.

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 the tool saves and emails receptionist-related content (phone script, IVR menu, etc.) and specifies it's for after specific tool usages, distinguishing it from siblings.

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

Usage Guidelines5/5

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

Explicitly states when to use (after write_phone_script, etc.) and when not (requires explicit consent, must ask first). Provides clear context and alternatives.

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?