Skip to main content
Glama

Open a prepared draft

get_work_product
Read-onlyIdempotent

Use to show a draft with its status (draft, edited by attorney, approved, rejected, out of date because a source changed) and its sources. 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": "get_work_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
work_product_idYes

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real value by disclosing what is returned (the draft, its status, its sources) and the enumerated status lifecycle including the 'out of date because a source changed' case, which no structured field conveys.

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 sentences, front-loaded with purpose before the exclusions, with no filler. The parenthetical status list is long but each value is informative rather than redundant.

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 simple, read-only, single-parameter tool with no output schema, the description covers purpose, return content, audience and exclusions adequately. The one real gap is how an agent obtains a valid work_product_id before calling.

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?

There is a single parameter with 0% schema description coverage, so the description carries the burden but says nothing about work_product_id — not its format, not where to obtain it, not that the 'wpr_' prefix identifies a work product. The pattern in the schema hints at format, but the description does not compensate for the missing coverage.

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?

States a specific verb and resource ('show a draft with its status ... and its sources') and enumerates the status values, so the agent knows exactly what comes back. It does not differentiate itself from the closest siblings (review_work_product, edit_work_product), only from search_attorneys, which is a distant concern.

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?

Provides explicit when-to-use ('Use to show a draft...') and when-not-to-use with a named alternative ('Do not call it for a person looking for a lawyer (use search_attorneys)'), plus an audience restriction. It stops short of telling the agent when to pick this over review_work_product or get_outstanding_work, which are the plausible confusions.

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