Skip to main content
Glama

Create writing style training

well_create_writing_style_training

Start learning the caller's writing style from their recent sent emails, in the background. When the person mentions their writing style or tone, offer to learn it; call this tool only when they ask for it or agree. The status means: "started", it runs for a few minutes and later drafts use it; "running", it is already learning; "recently_trained", the style was learned from their emails in the last 7 days and Well refreshes it on its own later; "needs_gmail", ask them to connect Gmail so Well can learn how they write; null, say in one line that Well can't start it right now, with no reason.

Input Schema

NameRequiredDescriptionDefault
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
idempotency_keyNoOptional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

NameRequiredDescriptionDefault
codeNo
errorNo
statusNoWhat happened to the style training: started, running, recently_trained, needs_gmail, or null when Well cannot start it now.
successYes
reply_linesNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
near_candidatesNo
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.
near_candidates_truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only say it is a non-destructive write; the description adds the real behavior an agent needs: it runs in the background for a few minutes, later drafts pick it up, refreshes happen automatically, and Gmail may be required. It even defines every status the caller can receive and what to say for each, including the null case.

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?

Purpose is front-loaded, followed by the invocation rule and status semantics. The status enumeration is long but each entry conveys distinct behavioral meaning; minor density cost only.

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 background-job tool with an output schema, the description covers initiation rules, timing expectations, downstream effect on drafts, the Gmail prerequisite, and fallback messaging. Nothing essential to correct invocation is missing.

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% and the four parameters (workspace_id, conversation_id, idempotency_key, workspace_scope) are documented in the schema itself. The description adds nothing parameter-specific, so the baseline applies.

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 action and object: start learning the caller's writing style from recent sent emails, in the background. This distinguishes it clearly from sibling tools like well_write_in_my_voice (apply a style) and well_record_writing_feedback (capture feedback).

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

Usage Guidelines4/5

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

Gives explicit triggering context (the person mentions their writing style or tone, offer to learn it) and a strong constraint (call only when they ask or agree), which prevents premature invocation. It doesn't name a sibling as an alternative, but the gating rule is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources