Skip to main content
Glama

signvoy_get_audit_trail

Read-only

Return the append-only audit trail for a document. Each entry records who did what and when (send, view, sign, decline, void, expire, remind). Useful for verifying chain of custody.

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_get_audit_trail"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_idYesDocument UUID from signvoy_list_documents.
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

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description still adds real value by declaring the trail append-only (immutable, complete history) and naming the event vocabulary an agent will receive. It omits ordering guarantees, volume/pagination, and retention, which keeps it short of a 5.

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, front-loaded with the return value, followed by the event vocabulary and the use case. No filler and nothing redundant with the structured fields.

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?

With no output schema, the description takes on the job of sketching the return shape, and it does ('each entry records who did what and when'), which is enough to call the tool correctly. Pagination and ordering for a potentially long append-only log are 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% and the schema itself already explains the document_id source and the workspace_id fallback behavior, so the description adds nothing on parameters. 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?

States a specific verb and resource ('Return the append-only audit trail for a document') and enumerates the recorded event types, which lets an agent distinguish this full-history tool from a status snapshot like signvoy_get_document_status without opening either 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?

Supplies a motivating context ('Useful for verifying chain of custody') but never states when to prefer this over the status or reminder siblings, nor any preconditions. Usage is implied rather than directed.

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