Skip to main content
Glama

signvoy_list_templates

Read-only

List templates in the workspace. Returns a summary per template (id, name, hasPublishedVersion). Only templates with hasPublishedVersion=true can be used to create documents. Call signvoy_get_template on the chosen template to retrieve recipient role keys before creating a document. Defaults to active (non-archived) templates.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (1–100, default 20).
statusNoFilter by template status. Default: active.
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.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint, so the description carries the rest: it names the returned fields (id, name, hasPublishedVersion), states the default active filter, and flags the published-version precondition for downstream document creation. Missing pagination/truncation behavior beyond the schema's limit cap, so not 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with purpose and followed by return shape, precondition, and next step. Slightly redundant that the active default is stated in both the description and the status parameter, but nothing is wasted overall.

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, yet the description enumerates the returned summary fields, which is the key gap it needed to fill. Combined with the published-version precondition and the hand-off to get_template, an agent has enough to call this correctly; only pagination behavior is left implicit.

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 already documents limit, status enum, and workspace_id fallback behavior. The description's only parameter-relevant addition is restating the active default, which duplicates the schema's status description, 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?

States a specific verb and resource ('List templates in the workspace') and immediately clarifies scope (defaults to active, non-archived). It is clearly distinguishable from signvoy_get_template, which it names as the follow-up call for a single template.

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?

Embeds an explicit workflow: use this to discover templates, note that only hasPublishedVersion=true ones are usable for document creation, then call signvoy_get_template for recipient role keys. That is concrete when-to-use and next-step guidance rather than a bare description.

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