Scribe Mail

Start the first signature from the company's brand

create_first_signature

Start a workspace's first email signature the way Scribe's web onboarding does: it looks up the company behind the user's email domain (name, logo, brand color and style, button labels, social links, phone, address, the person's name and job title) and builds the onboarding's template that suits the brand, saved as a DRAFT and returned rendered so you can show it. Use it right after create_scribe_account, or for a workspace that has no signature yet. Never publishes: publish_signature only after the person approves.

Input Schema

Name	Required	Description	Default
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`create_another`	No	Create it even though the workspace already has a signature (default false: report it instead). Only when the person asked for a new starting point.

Output Schema

Name	Required	Description
`data`	Yes
`signature`	Yes	The draft signature created; null when nothing was created.
`next_steps`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the write and open-world annotations, it discloses the company lookup from the user's email domain, the data collected, template generation, DRAFT persistence, and the rendered result for review. "Never publishes" and the approval condition clarify that invocation does not make the signature live.

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 purpose is front-loaded, and the following sentences efficiently cover timing and publication safety. The long parenthetical inventory makes the opening sentence dense, but its details are relevant and there is no repetitive filler.

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?

For a two-parameter creation tool with complete input and output schemas, the description supplies the essential operational context: brand-data provenance, draft creation, rendered preview, workflow position, and approval boundary. The existing-signature exception is covered by create_another, and no additional return-value explanation is necessary.

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%, and both context and create_another are thoroughly documented there, making 3 the appropriate baseline. The description explains the implicit brand-data source but adds no direct guidance about either explicit parameter, including create_another's override-versus-report behavior.

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 opening identifies a specific operation and resource: starting a workspace's first email signature using brand-derived web-onboarding behavior. References to create_scribe_account and publish_signature also place it clearly within the signature workflow rather than leaving it interchangeable with other signature tools.

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?

It gives explicit invocation points: immediately after create_scribe_account or when a workspace has no signature yet. It also establishes an approval gate and directs publishing to publish_signature, while the schema documents the exceptional create_another case.

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

All Scribe Mail tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.