Skip to main content
Glama

New document from letterhead

clio_document_create_from_letterhead

Create a new document in a Clio matter from a letterhead or template, insert your text, and upload it to the matter folder.

Instructions

Creates a new document in a matter from a letterhead / template (Document Template in Clio): selected by template_id or template, otherwise by configuration (user → template map, default template, kind=internal → internal template). RECOMMENDED APPROACH (works everywhere, even without disk access): pass the finished text in the content parameter – the server inserts it into the letterhead (docx) and uploads it to the "Claude" folder in the matter (preview, then confirm with the token). content format: empty line = empty paragraph; '# ' / '## ' / '### ' = Heading 2/3/4 of the template; bold; '[ 1. ] text' = numbered paragraph (number in the margin, text with a hanging indent); 'Label:: text' = bold label + tab; '- ' bullet; '\t' tab; '---pagebreak---' page break; ':::center text' centred, ':::right text' right-aligned. Follow the user's conventions for the document structure (addressee, reference numbers, date, heading, enclosures) if they state them. Alternatives: without content, mode='download' only downloads the template for manual editing (Cowork with a connected folder); mode='automation' lets Clio generate the document via Document Automation. Without a letterhead only with without_letterhead=true. Do not create empty documents: if the user has not provided the text (and the document type, addressee, matter), ask before calling this tool. mode='download' serves only a user who will edit the file in a connected folder (Cowork) – never download a template just to upload it unchanged. Choose filename from the document type and addressee (e.g. 'Letter_to_opposing_counsel_2026-10-03.docx') unless the user names it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNouser = letterhead of the signed-in user (default), internal = internal template
modeNodownload (default) = download the template for editing; automation = generate in Clio via Document Automation
confirmNoconfirm=true performs the write. Use it directly when the user's request contains everything needed; call without confirm (preview) only when you want to check the data first or something is unclear.
contentNoFinished document text (markdown-lite, see description). If provided, the server fills the letterhead and uploads the document to Clio. Never pass empty or placeholder text – if the user has not said what the document should contain, ask first.
formatsNoAutomation only: original = template format (docx), pdf; default ['original']
filenameYesName of the new document including the extension, e.g. 'Statement of defence.docx'
templateNoTemplate name or name prefix (overrides automatic selection); alternative to template_id
matter_idYesID of the matter the document belongs to
target_dirNoCustom target folder on the PC (absolute path), e.g. a folder connected in Cowork; default work folder/matter
template_idNoExplicit template id (overrides automatic selection)
keep_local_copyNotrue = also save the filled file to the work folder (default true)
without_letterheadNotrue = do not use a template (only returns instructions for uploading a plain file)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • changedInput schema / properties / confirm / description
      Previous value: -"Leave out on the first call: the tool returns a PREVIEW with a confirmation token. Show the preview to the user, wait for their explicit approval, then repeat the call with identical arguments and confirm set to that token. confirm=true is not accepted."New value: +"confirm=true performs the write. Use it directly when the user's request contains everything needed; call without confirm (preview) only when you want to check the data first or something is unclear."
  2. First observedv1.0.0-beta.1

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the whole burden and does well: it discloses the preview-then-confirm token flow, the upload destination ('Claude' folder in the matter), that content triggers the server-side letterhead fill, and the local-copy behavior. It does not cover permission requirements or failure modes, so not quite a 5.

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-loaded with the core action and the recommended approach, and the content-format list is genuinely necessary detail. It is dense and long for one tool, with a couple of parenthetical asides that could be trimmed.

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

Completeness4/5

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

For a 12-parameter mutation tool with no output schema and no annotations, the description covers mode selection, template resolution order, content format, and filename policy well. Remaining gaps are relatively minor: no mention of what the preview returns or permission prerequisites.

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 schema baseline is 3, but the description adds real value beyond it by defining the markdown-lite content grammar (headings, bold, numbered paragraphs, page breaks, alignment) and the filename convention that the schema does not spell out.

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 ('Creates a new document in a matter from a letterhead / template') and immediately distinguishes itself from sibling write tools by explaining the letterhead/template-fill mechanism. An agent can tell it apart from clio_document_upload and clio_document_write.

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 routes between modes ('download' only for manual editing in a connected folder; 'automation' to let Clio generate) and against the no-template path (without_letterhead=true). It also states a negative condition: do not create empty documents, ask before calling if text/type/addressee are missing.

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