Skip to main content
Glama

signvoy_remind_document

Send an immediate reminder email to all pending recipients of a sent document. Only available for documents in 'sent' or 'in_progress' status. 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>"
    },
    "name": "signvoy_remind_document"
  }
}

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations declare idempotentHint=false and destructiveHint=false, so the safety profile is partly covered. The description adds real value the annotations cannot: this triggers an outbound email to external recipients immediately, is status-gated, and should not be repeated carelessly — consistent with the non-idempotent hint. It still omits whether there is a cooldown or rate limit per document and what happens when no recipients are pending.

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?

Three short sentences, with the action and recipient scope front-loaded and the constraint and caution following. Every sentence adds information; nothing is padded or repeated from the title.

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, fully documented action with no output schema, the description covers the action, the eligibility gate, and the misuse risk. A brief note on the response (e.g., count of recipients reminded, or failure when none are pending) would close the remaining 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 coverage is 100%, including the UUID pattern and the note that workspace_id may be omitted only for single-workspace users with a pointer to signvoy_list_workspaces, so the schema carries the parameter burden. The description adds only that the reminder targets all pending recipients, not per-recipient selection. Baseline 3 is appropriate.

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?

The description uses a specific verb and resource ('Send an immediate reminder email to all pending recipients of a sent document') and its 'all pending recipients' scope implicitly separates it from the single-recipient sibling signvoy_remind_recipient. It stops short of naming that alternative outright, so the differentiation must be inferred rather than read.

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?

It states a clear precondition ('Only available for documents in sent or in_progress status') and a caution against overuse ('Use sparingly — do not spam recipients'), which tells the agent when-not to call. It does not, however, route the agent to signvoy_remind_recipient when only one signer needs a nudge.

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