Skip to main content
Glama

Prepare a draft for attorney review

prepare_work_product
Idempotent

Use to prepare a chronology, issue matrix, missing-document list, client email draft or research question list from the inquiry's documents. It is a draft for a lawyer to review, never sent or filed. Research lists name no case law or statute. For a lawyer or staff member of a law office signed in to ESQ CoPilot for their office. Do not call it for a person looking for a lawyer (use search_attorneys) or for general legal questions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "matter_id": "<matter_id>",
      "kind": "<kind>"
    },
    "name": "prepare_work_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
matter_idYesThe inquiry (matter) id from the briefing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the write-and-idempotent profile is covered structurally. The description adds meaningful context beyond that: output is a draft for lawyer review, never sent or filed, and research plans deliberately cite no case law or statute. It stops short of saying where the draft is stored or what is returned for subsequent review, which is the only remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with 'Use to prepare...', then scope/safety guarantees, then audience and exclusions. Every sentence carries distinct information an agent needs; no repetition of the title or annotations.

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 drafting tool with no output schema, the description covers purpose, artifact types, audience/auth, non-delivery guarantee, content constraints, and explicit out-of-scope routing. An agent has everything needed to decide to call it and with which kind.

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 50%: matter_id is documented in the schema but the kind enum has no per-value descriptions. The description compensates by spelling out the artifacts in prose that correspond to the enum values and by adding a constraint on research_plan output. It does not explain the matter_id format beyond what the schema already gives.

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 ('prepare') and enumerates the concrete artifacts produced (chronology, issue matrix, missing-document list, client email draft, research question list), which map one-to-one to the kind enum. This makes it clearly distinguishable from siblings such as review_work_product, edit_work_product, or prepare_case_brief.

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 explicit when-to-use (prepare drafts from the inquiry's documents), who may use it (a lawyer or staff member of a law office signed in to ESQ CoPilot), and two named exclusions with a routing alternative – search_attorneys for people seeking a lawyer, and general legal questions. Nothing is left to inference.

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