Skip to main content
Glama

Send the approved reply to the client (lawyer's yes needed)

send_office_reply
DestructiveIdempotent

Use only right after the signed-in LAWYER said yes to the exact text shown by preview_office_reply. Sends exactly that text, once, into the person's private ESQ CoPilot thread. Refused for staff, for a changed draft, after 15 minutes, or if the inbox is off. Report the status exactly as returned (sent means stored in the person's thread, not read). 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": {
      "preview_id": "<preview_id>",
      "payload_sha256": "<payload_sha256>",
      "idempotency_key": "<idempotency_key>",
      "lawyer_said_yes_to_exact_text": "<lawyer_said_yes_to_exact_text>"
    },
    "name": "send_office_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
preview_idYes
payload_sha256Yes
idempotency_keyYes
lawyer_said_yes_to_exact_textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the annotations (destructiveHint, idempotentHint, openWorldHint) by enumerating the refusal conditions: staff callers, a changed draft, more than 15 minutes elapsed, or an inbox that is off. It also defines the return semantics ("sent means stored in the person's thread, not read") and instructs the agent to report status verbatim, which annotations cannot convey.

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-loads the critical precondition ahead of refusal rules and audience limits, which is the right ordering for a guarded write. It is dense but nearly every clause is load-bearing; only the closing audience sentence partly overlaps with the opening precondition.

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?

Covers the operational envelope an agent needs for a high-risk write tool: gating precondition, expiry window, refusal cases, and status interpretation, with no output schema to duplicate. The one material hole is the unexplained cryptographic and idempotency parameters, which matter because all four are required.

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 4 required parameters, so the description must carry the meaning and largely does not. It implies preview_id originates from preview_office_reply, but payload_sha256, idempotency_key, and lawyer_said_yes_to_exact_text (a const-true boolean) are never explained, leaving the agent to guess at hashing and retry-key construction.

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 ("Sends exactly that text, once, into the person's private ESQ CoPilot thread") and explicitly separates itself from preview_office_reply (which shows the text) and from search_attorneys (for people seeking a lawyer). An agent can identify the operation and its scope without opening any 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?

Gives an explicit trigger ("only right after the signed-in LAWYER said yes to the exact text shown by preview_office_reply"), explicit exclusions (changed draft, staff, person looking for a lawyer, general legal questions), and names the correct alternative (search_attorneys) for one of them. Both when-to-use and when-not-to-use 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