Skip to main content
Glama

Remind signers who have not signed

remind_recipients

Re-send the signature request email to recipients who haven't signed yet (at most once an hour per recipient). Uses no extra envelopes.

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

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. 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

A4/5.0
Behavior4/5

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

Beyond the annotations (which only declare write, non-idempotent, non-destructive, open-world), the description discloses two operational facts an agent cannot get elsewhere: a per-recipient throttle of once an hour and that no additional envelopes are consumed. It stops short of saying what happens when zero recipients remain unsigned or whether a call is rejected versus silently no-oping.

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?

A single sentence with the audience and the throttle in parentheses; nothing is repeated from the title and the scoping condition is front-loaded.

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 two-parameter, annotation-covered tool with no output schema, the description supplies the essentials: who gets emailed, the rate cap, and the envelope-quota implication. Only the failure/empty-set behavior is left unstated, which is a minor gap.

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 both parameters are already fully documented in the schema, including the api_key account-override and fallback-auth rationale. The description adds no meaning about document_id beyond the schema, so the baseline 3 applies.

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 ('Re-send the signature request email') and a precisely scoped resource ('recipients who haven't signed yet'), which distinguishes it from send_document (initial send) and test_send_document 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 Guidelines3/5

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

Usage is implied rather than stated: the parenthetical about unsigned recipients and the schema note that the document 'Must be a sent document awaiting signatures' tell the agent the precondition, but there is no explicit when-to-use vs. when-not-to-use guidance or named alternative.

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.