Skip to main content
Glama

Preview sending an approved draft to the client (nothing is sent)

preview_office_reply
Read-onlyIdempotent

Use when the lawyer wants to send an APPROVED client email draft as the office's reply. Returns the recipient, the complete text and a preview_id and payload_sha256. Sends NOTHING. Show all of it; only after the lawyer clearly says yes to these exact words call send_office_reply. 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": {
      "work_product_id": "<work_product_id>"
    },
    "name": "preview_office_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
work_product_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/non-destructive, but the description adds the crucial guarantee ('Sends NOTHING'), names the returned fields (recipient, complete text, preview_id, payload_sha256) in the absence of an output schema, and mandates a confirmation gate before calling send_office_reply. It also scopes the audience to signed-in law-office staff, which is behavioral context not present in the structured fields.

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 trigger and the key safety fact ('Returns... Sends NOTHING'), and every clause carries distinct information. Slightly dense with the audience-scoping sentence at the end, but nothing is wasteful.

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 one-parameter read-only preview with no output schema, the description supplies the return fields, the safety guarantee, the confirmation workflow, and the audience boundary. An agent has everything needed to call it and to know what to do next.

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 0% and the single parameter is undocumented in the schema itself; the description compensates only indirectly by implying the id refers to an APPROVED client email draft. The wpr_ prefix format and constraints live only in the schema pattern, not the prose.

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 ('preview sending an approved client email draft as the office's reply') and implicitly separates itself from send_office_reply by the 'Sends NOTHING' clause. An agent can distinguish preview from send without opening either 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?

Explicit trigger ('Use when the lawyer wants to send an APPROVED client email draft'), an explicit exclusion with a named alternative ('Do not call it for a person looking for a lawyer (use search_attorneys)'), a second exclusion for general legal questions, and an explicit hand-off condition to send_office_reply after the lawyer confirms.

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