Skip to main content
Glama

Void (cancel) a sent document

void_document
DestructiveIdempotent

Cancel a sent document that is still awaiting signatures. Recipients who haven't signed are told it was cancelled.

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": "void_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoOptional reason shown to recipients.
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. Must be a sent document awaiting signatures.

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. Must be a sent document awaiting signatures."
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds a genuinely useful consequence beyond them: unsigned recipients are notified that the document was cancelled. It stops short of saying what happens to already-signed recipients or whether the void is reversible.

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 sentences, zero waste, with the precondition and the recipient-facing effect both front-loaded. Nothing repeats the annotations or the schema.

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 single-required-parameter mutation with rich annotations and full schema coverage, this covers purpose, eligibility, and side effect. The only meaningful gap is behavior on partially signed documents and whether the action can be undone.

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 coverage is 100%, so all three parameters are fully documented in the schema itself, including the multi-account api_key behavior and the document_id provenance. The description adds only the "still awaiting signatures" constraint, which is already restated in the document_id schema text, so the baseline 3 applies.

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?

"Cancel a sent document that is still awaiting signatures" gives a specific verb (cancel) plus resource (sent document) plus a state precondition. It is clear enough to distinguish from send_document or get_document, though it never explicitly contrasts with the sibling delete_document, which an agent could plausibly confuse it with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The precondition "still awaiting signatures" implies when the tool is applicable, which is real guidance. However, there is no explicit statement of when not to use it, no mention of what to do for a document that is already fully signed, and no routing to delete_document as the alternative for other cases.

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.