Skip to main content
Glama

Invite your own lawyer to review

share_with_attorney

Invite a lawyer of the user's choice, by e-mail, to review the contract in Dealroom's attorney review. Available to any lawyer the user invites. The lawyer works for the user and bills the user directly; Dealroom takes no fee. Signing waits until the lawyer approves or the user cancels the review in Dealroom. Free (no credit).

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": {
      "dealId": "<dealId>",
      "email": "<email>"
    },
    "name": "share_with_attorney"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the e-mail; left out, the contract's language
nameNoThe lawyer's name, for the e-mail greeting
emailYesThe lawyer's e-mail address
dealIdYesAgent deal id (dealId from generate_contract)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses key behavioral details: the lawyer works for the user, bills the user directly, Dealroom takes no fee, the invite is free with no credit, and signing is blocked until approval or cancellation. These are important operational consequences not captured by readOnlyHint or openWorldHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and then adds relevant constraints without wasted words. Each sentence contributes useful context about billing, approval, and cost.

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 an action tool with no output schema, the description covers who can be invited, the billing relationship, the approval gate, and the cost. It gives an agent enough information to use the tool correctly without needing return-value details.

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 100%, so the input schema already documents dealId, email, name, and lang clearly. The description adds context about the invitation but does not add parameter-level meaning beyond the schema, which is sufficient for a baseline score.

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?

The description states a specific verb and resource: inviting a lawyer by e-mail to review the contract in Dealroom's attorney review. It clearly distinguishes this from sibling tools like generate_contract or download_contract by focusing on inviting an external reviewer.

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?

It explains that the tool is available to any lawyer the user invites and that signing waits until the lawyer approves or the user cancels. It does not explicitly name an alternative tool, but it gives clear contextual conditions for use.

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.