Skip to main content
Glama

Approve or reject a draft (lawyer only, needs their yes)

review_work_product
Destructive

Use only after the lawyer clearly said to approve or reject this exact version. Staff cannot approve. A draft whose sources changed cannot be approved. 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>",
      "decision": "<decision>"
    },
    "name": "review_work_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
decisionYes
work_product_idYes
expected_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds the authorization gate (a lawyer must have verbally instructed approval) and a state precondition (stale sources block approval), which annotations cannot express. It stops short of saying what happens to the draft or the note after a rejection, so it is not fully exhaustive.

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?

The authorization requirement is front-loaded in the first sentence, followed by qualifiers and then exclusions, which is the right order. Each sentence carries a distinct rule with no filler. The clipped fragment style ('Staff cannot approve.') is dense but readable.

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?

There is no output schema, so the description should ideally say something about the result, and it does not. However, for a destructive mutation the critical unknowns are authorization, preconditions, and side effects; authorization and preconditions are covered thoroughly, with only the post-call outcome left implicit, and the destructiveHint annotation signals irreversibility.

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 four parameters, so the description carries the full burden. 'This exact version' is the only real addition, implying that expected_version pins the approval to the version the lawyer reviewed, but work_product_id, its format, and note's purpose and 1000-char limit are left entirely to the schema. The decision enum is self-explanatory.

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 pair and resource: approving or rejecting a draft, specifically 'this exact version'. It also routes away from a sibling ('use search_attorneys'), so an agent can separate it from edit_work_product or get_work_product. It never names the tool's own artifact type in the same terms as the schema (work_product_id), but the intent is unmistakable.

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 when-to-use ('only after the lawyer clearly said to approve or reject this exact version'), explicit who-cannot ('Staff cannot approve'), an explicit preclusion ('a draft whose sources changed cannot be approved'), and explicit when-not with a named alternative ('use search_attorneys' for people seeking a lawyer, and not for general legal questions). Both positive and negative routing are covered.

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