Scribe Mail

Create a Scribe account

create_scribe_account

Create the Scribe account of the person signed in to this connector, when they have none yet (other Scribe tools say so). Creates their workspace with a free 14-day trial, from the email they signed in with, which must be a company address. ONLY call it after: (1) the person said they do NOT already have a Scribe account (someone who has one must reconnect with their Scribe email instead, or they get a second, empty workspace); (2) you showed them the Terms and Conditions (https://www.scribe-mail.com/terms-and-conditions) and the Privacy Policy (https://www.scribe-mail.com/privacy-policy); and (3) they explicitly agreed to create the account. Pass accept_terms: true only then.

Input Schema

Name	Required	Description
`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."
`time_zone`	No	The person's IANA time zone (e.g. America/Chicago), when you know it.
`accept_terms`	Yes	Must be true, and only once the person explicitly agreed in the chat to the Terms and Conditions and the Privacy Policy.

Output Schema

Name	Required	Description	Default
`data`	Yes
`next_steps`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 28, 2026
- removedOutput schema / properties / data / properties / trial_ends_at / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / trial_ends_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / user / properties / first_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / user / properties / first_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / user / properties / last_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / user / properties / last_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / workspace / properties / name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / workspace / properties / name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
AddedOct 28, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare the generic safety profile (readOnlyHint=false, openWorldHint=true, destructiveHint=false), so the description carries the real burden and does: it discloses the 14-day free trial workspace creation, the company-address constraint on the sign-in email, and the concrete failure consequence of getting it wrong — 'a second, empty workspace'. That is exactly the risk context an agent needs before a non-idempotent write.

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?

Front-loads the action and scope, then presents the preconditions as a numbered list, so the length is justified by genuine consent requirements. The parenthetical '(other Scribe tools say so)' is slightly oblique and the block could be lightly trimmed, keeping it off a 5.

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 non-idempotent, open-world account-creation write with an output schema already covering return values, the description covers purpose, consent prerequisites, side-effect risk, and eligibility constraints. Nothing an agent needs before invoking it is missing.

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 the baseline is 3; the description goes further by tying accept_terms to the consent evidence ('Pass accept_terms: true only then'), which tells the agent the gating semantics rather than just the type. It says nothing extra about time_zone or context beyond the schema, so it stops short of a 5.

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?

States a specific verb and resource ('Create the Scribe account of the person signed in to this connector') plus the scope condition ('when they have none yet'), which distinguishes it from every other create_* sibling. An agent knows exactly what this tool produces without opening the schema.

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?

Gives an explicit three-part precondition list (user denies having an account, terms and privacy policy were shown, explicit agreement) and names the alternative path for users who already have an account ('reconnect with their Scribe email instead'). Both when-to-use and when-not-to-use are covered.

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.