Skip to main content
Glama

signvoy_remind_recipient

Send an immediate reminder email to a specific pending recipient. Use this when you want to remind only one person instead of all pending recipients. Only available for documents in 'sent' or 'in_progress' status. Rate limited to 1 reminder per recipient per 24 hours. Check recipients[].lastRemindedAt from signvoy_get_document_status to avoid rate limit errors. Only remind recipients where hasActiveSigningLink is true (respects sequential signing order). Use sparingly — do not spam recipients.

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>",
      "document_recipient_id": "<document_recipient_id>"
    },
    "name": "signvoy_remind_recipient"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_idYesDocument UUID to remind. Must be in 'sent' or 'in_progress' status.
workspace_idNoTarget workspace UUID. Safe to omit only when the user belongs to exactly one workspace; required otherwise, and omitting it then fails with the list of candidates. Call signvoy_list_workspaces to find it.
document_recipient_idYesRecipient UUID from signvoy_get_document_status recipients[].id. Recipient must be in 'pending' status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only supply idempotentHint=false, destructiveHint=false, and a title; the description adds the substantive behavior: a 24-hour per-recipient rate limit, status prerequisites, sequential-signing-order enforcement, and the exact call needed to verify eligibility beforehand. Nothing here contradicts the annotations — the non-idempotent hint is consistent with the stated rate limit and external email side effect.

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 the single-vs-bulk distinction, then layered constraints in descending importance. Slightly dense at six sentences, and 'Use sparingly — do not spam recipients' partly restates the 24-hour rate limit, though it adds appropriate tone for an outbound-email action.

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?

No output schema exists, and the description never indicates what a successful call returns (e.g., confirmation or updated reminder timestamp), which is the one gap for an agent verifying the result. Otherwise the preconditions, rate limit, and sequencing rules cover everything needed to invoke it safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real selection semantics beyond the schema: the recipient must be pending, must have hasActiveSigningLink true, and the id comes from recipients[].id in signvoy_get_document_status. It does not add much about workspace_id resolution, which the schema already documents thoroughly.

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, resource, and scope: send an immediate reminder email to a single pending recipient. It explicitly distinguishes itself from the bulk alternative ('remind only one person instead of all pending recipients'), which maps cleanly onto the sibling signvoy_remind_document.

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

Usage Guidelines5/5

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

Gives when-to-use (single recipient vs. all), hard preconditions (document must be in 'sent' or 'in_progress'), a rate-limit constraint with a concrete pre-check (recipients[].lastRemindedAt from signvoy_get_document_status), and a sequencing gate (hasActiveSigningLink must be true). It also names the alternative behavior implicitly and warns against overuse, leaving little to inference.

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