Skip to main content
Glama

Save the attorney's edits to a draft

edit_work_product

Use only to save words the member wrote or clearly approved. Creates a new version marked as edited by the attorney; earlier versions are kept. 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>",
      "expected_version": "<expected_version>"
    },
    "name": "edit_work_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
subjectNo
body_textNo
attorney_noteNo
work_product_idYes
expected_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and non-idempotent, so the write/safety profile is covered structured-data-side. The description adds real value on top: it discloses versioning behavior ('creates a new version... earlier versions are kept', consistent with destructiveHint=false) and imposes a content-provenance policy on what may be saved. It says nothing about optimistic-concurrency failure behavior, which matters because a required expected_version token exists.

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?

Three short sentences, front-loaded with the hard usage constraint and then the versioning behavior, followed by audience and exclusions. Little waste, though the audience sentence is largely boilerplate compared with the more actionable parameter and conflict information that is missing.

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

Completeness3/5

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

For a five-parameter mutation tool with no output schema and zero schema descriptions, the description covers purpose, who may call it, and non-destructive versioning, which is a reasonable core. It is still incomplete on the pieces an agent most needs to invoke correctly: the meaning of expected_version and what to do when it mismatches, plus the roles of subject and attorney_note.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, so the description carries the full burden and largely fails: it never explains work_product_id, expected_version, subject, body_text or attorney_note. 'Save words' weakly implies body_text is the edited content, but the concurrency contract behind expected_version and the distinction between body_text and attorney_note are left entirely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('save words the member wrote', creating 'a new version marked as edited by the attorney') and reinforces it with the title. It also names a sibling it is not (search_attorneys), so an agent can separate it from the read/draft siblings, though the description never explicitly contrasts it with get_work_product, prepare_work_product or review_work_product.

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?

There is an explicit gating condition ('Use only to save words the member wrote or clearly approved') plus an audience constraint and two named exclusions with a redirect to search_attorneys. The exclusions address consumer-style lookups rather than the more obvious draft-related siblings, so the routing guidance is clear but does not cover the closest alternatives.

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