Skip to main content
Glama

onboarding_questionnaire

Send a structured onboarding questionnaire email to collect client goals, assets, and preferences, minimizing back-and-forth and accelerating project start.

Instructions

Write the onboarding questionnaire email sent to a new client right after they sign the contract. Gathers everything you need to start work: goals, target audience, brand assets, access credentials, tone/style preferences, examples they like or dislike, key contacts, and approval workflow. Includes optional custom questions for project-specific needs. Avoids the back-and-forth that slows down project starts and sets a professional tone from day one. Does not count against your monthly draft limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_nameYesFirst name or full name of the client
project_nameYesName of the project
due_dateNoDate by which you need the questionnaire returned (e.g. 'Friday 20 June', 'by end of week')
kickoff_dateNoPlanned project kickoff or start date — used to frame why the deadline matters
access_neededNoSpecific access or credentials you'll need (e.g. 'CMS login, Google Analytics, brand asset folder')
brand_assets_neededNoWhether to ask for brand assets (logo, fonts, colours, guidelines) — defaults to true
custom_questionsNoAny project-specific questions to append (e.g. 'Who is the primary approver for copy?', 'Do you have existing customer personas?')
your_nameNoYour name for the sign-off
Behavior3/5

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

With no annotations, the description carries full burden. It notes that 'does not count against your monthly draft limit' but does not clarify whether the tool sends the email or just generates its content. Missing details on permissions, side effects, or delivery behavior.

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 description is well-structured, starting with the main action and then listing details. It is concise enough to convey key points without extraneous content, though it could be slightly shorter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description gives good context for when to use and what the tool accomplishes, but it does not specify the output (e.g., returns email text) or how the result is presented. Without an output schema, this information would be helpful for an AI agent.

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 is 3. The description adds context (e.g., examples of what to ask) but does not provide significant new meaning beyond the already descriptive schema parameter descriptions.

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 writes an onboarding questionnaire email for new clients after contract signing, listing specific items gathered. It distinguishes from sibling tools like client_onboarding_checklist by focusing on an email that collects information, not a checklist.

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 use after contract signing but does not explicitly state when to use this tool versus alternative onboarding or email tools. No exclusions or alternative tool names are provided.

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/jabbawocky/proposalcraft'

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