Skip to main content
Glama

signvoy_list_documents

Read-only

List documents in the workspace, newest first. Returns a summary per document (id, name, status, recipient counts). Members only see their own documents; admins and owners see all.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "signvoy_list_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSearch by document name or recipient email.
limitNoMax results (1–100, default 20).
offsetNoZero-based offset for pagination.
statusNoFilter by document 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.8/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 adds real context beyond that: the newest-first ordering, the per-document summary fields returned (id, name, status, recipient counts), and role-based result visibility. It does not mention pagination behavior or total counts, which is a moderate remaining gap but not a contradiction.

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?

Three short sentences, each earning its place: scope/ordering, return shape, then visibility rules. Front-loaded with the core action and no redundant restatement of the tool name or 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?

With no output schema, the description correctly compensates by summarizing the returned fields, and the schema fully documents the five optional parameters with defaults and bounds. What remains unstated is pagination/total-count semantics and whether the list is workspace-scoped only, but for a read-only list tool this is close to complete.

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%, including a detailed workspace_id note that points at signvoy_list_workspaces, so the schema does all the parameter work. The description's only parameter-adjacent signal is the phrase "in the workspace," adding essentially nothing beyond what is already structured. 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?

States a specific verb and resource ("List documents in the workspace") plus ordering ("newest first"), which cleanly separates it from siblings like signvoy_get_document_status or signvoy_list_contacts. It stops short of naming an alternative list/GET sibling explicitly, so the differentiation is implied by the resource noun rather than spelled out.

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 description gives useful context about who sees what ("Members only see their own documents; admins and owners see all"), but that is visibility scoping rather than when-to-use guidance. There is no statement of when to prefer this over signvoy_list_templates, signvoy_get_document_status, or a filtered search, and no prerequisites or exclusions are given.

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