Skip to main content
Glama

send_document

Email a Draft document (agreement/NDA/terms) to its client for electronic acceptance — the client reviews it, types their name, and the acceptance is archived with a certificate. CONFIRM with the user before calling — this emails a real person.

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": {
      "id": "<id>"
    },
    "name": "send_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does meaningful work: it discloses an irreversible external side effect (a real email to a real person), a required confirmation step, and downstream consequences (e-signature by typed name, archived certificate). It does not cover error cases, resend/retry behavior, or what happens if the document is not in draft, which keeps it from a 5.

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-loaded with the action and outcome, then closes with the safety warning, which is the right ordering for an agent scanning it. Every clause adds information; only the stray internal whitespace and the slightly run-on first sentence cost it a point.

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 single-parameter tool with no annotations and no output schema, the description covers the action, the recipient, the e-signature flow, the archival artifact, and the human-confirmation gate. Only the return value and the failure/eligibility conditions are unaddressed, which is a minor gap at this complexity.

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?

The schema has one required parameter at 0% description coverage, so the description must supply the meaning. It implies the id refers to the Draft document being sent, but never states this explicitly, nor does it specify id format (the schema says uuid but neither text confirms the identifier's target). Adequate but leaves an inference.

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 ("Email a Draft document"), names the document kinds in scope (agreement/NDA/terms), and describes the full outcome (client types name, acceptance archived with certificate). An agent can distinguish this from send_invoice or the list_* tools 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word "Draft" implies a precondition (only draft-state documents), and the description adds an explicit operational rule: "CONFIRM with the user before calling." It does not name a sibling tool as an alternative or state what to do for non-draft documents, so it falls short of full when/when-not guidance.

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