Skip to main content
Glama

Email a test copy to yourself

test_send_document

Email a watermarked TEST copy of the signature request to the account owner only, so the human can see exactly what recipients will get. Free, uses no envelopes and needs no plan; limited to 10 a day.

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": {
      "document_id": "<document_id>"
    },
    "name": "test_send_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoAn md2sign API key. When given, this call uses that key's account even if the connection is signed in as someone else, so pass it on every call when your human has more than one md2sign account (for example two businesses). Also use it if your MCP client cannot send an "Authorization: Bearer <api_key>" header.
document_idYesThe document ID returned by create_draft, list_documents or create_document_from_template.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Your md2sign API key. Only needed if your MCP client cannot send an \"Authorization: Bearer <api_key>\" header."New value: +"An md2sign API key. When given, this call uses that key's account even if the connection is signed in as someone else, so pass it on every call when your human has more than one md2sign account (for example two businesses). Also use it if your MCP client cannot send an \"Authorization: Bearer <api_key>\" header."
  2. Changed1 schema field changed
    • addedInput schema / properties / document_id / description
      Added value: +"The document ID returned by create_draft, list_documents or create_document_from_template."
  3. First observed

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 (which already flag openWorldHint=true and idempotentHint=false) by disclosing cost and side effects: free, consumes no envelopes, needs no plan, and is capped at 10 per day. The 10/day quota and 'account owner only' recipient scope are exactly the operational facts an agent needs and cannot get from structured fields.

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?

Two tight sentences, front-loaded with the action and recipient scope, followed by the cost/quota facts. Every clause earns its place: watermark, owner-only, free, no envelopes, no plan, 10/day.

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 one might want a note on what the call returns or on document-state prerequisites (e.g. whether a void or completed document can be test-sent); otherwise the definition is complete for a two-parameter, non-destructive action.

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 description adds no parameter-level meaning; both parameters are already fully documented in the schema (100% coverage), including api_key's multi-account semantics and document_id's provenance. Baseline 3 is appropriate since the schema carries this burden.

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 concrete verb and resource ('Email a watermarked TEST copy of the signature request') plus a recipient constraint ('to the account owner only'), which makes the contrast with the real send_document sibling obvious without naming it. An agent can tell what this does and what it does not do (reach real recipients) from the first clause.

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?

Gives a clear usage context: use it so the human can see exactly what recipients will get. The implication that send_document handles the real delivery is strong but never stated explicitly, and there is no exclusion (e.g. document must be a draft, or when a test send is pointless).

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.