Skip to main content
Glama

signvoy_get_template

Read-only

Get full details of a single template including its recipient role keys. Role keys (e.g. 'signer', 'witness', 'approver') are required when calling signvoy_create_document — each recipient must be matched to a roleKey from this template. Always call this before create_document.

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": {
      "template_id": "<template_id>"
    },
    "name": "signvoy_get_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
template_idYesTemplate UUID from signvoy_list_templates.
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/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description does not contradict that. It adds real context beyond the annotations: the return contains recipient role keys with concrete examples ('signer', 'witness', 'approver') and the keys are a hard input requirement elsewhere. It stops short of describing the full response shape or error behavior, keeping it at a 4.

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, front-loaded with what is returned, followed by why the role keys matter and the ordering constraint. No redundant restatement of the title or name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read with no output schema and 100% schema coverage, the description supplies everything an agent needs: what comes back, why the key field matters, and that it must precede document creation. Nothing material is missing for correct invocation.

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%, and the schema itself documents template_id's source (signvoy_list_templates) and the workspace_id omission rule with its failure mode. The description adds nothing about either parameter, so the schema carries the load and 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 ('Get full details of a single template') and narrows scope to the distinguishing payload ('including its recipient role keys'). An agent can immediately tell this apart from signvoy_list_templates, which returns collections rather than one template's role keys.

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 an explicit prerequisite rule: 'Always call this before create_document,' and explains why — role keys are required to match each recipient in signvoy_create_document. This names both the condition for use and the sibling tool that depends on it, leaving no inference needed.

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