Skip to main content
Glama
Sign In
MCP Server for eSignatures. com

MCP Server for eSignatures. com

by esignaturescom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_template_collaborators

Retrieve collaborators for eSignature templates to manage editing access and permissions. Returns GUID, name, email, and edit links for each collaborator.

Instructions

Returns the list of template collaborators, including their GUID, name, email, and the HTTPS link for editing the template

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": "list_template_collaborators"
  }
}

Input Schema

NameRequiredDescriptionDefault
template_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the burden of indicating that this is a read operation; 'Returns' does suggest that, and the listed fields preview the response. However, it does not disclose permissions, error behavior, pagination, or behavior for an invalid template_id.

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?

A single front-loaded sentence states the operation and the most useful output fields with no filler, repetition, or unnecessary detail.

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 one-parameter list operation with no output schema, the description is largely complete: it identifies the input template and the returned collaborator fields. It lacks only minor semantics such as pagination or error behavior, which are less critical for a simple list tool.

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?

The schema provides only a required string template_id with 0% coverage, so the description must compensate. It indirectly clarifies that the parameter identifies the template whose collaborators are listed, but it does not explicitly describe the parameter's meaning, format, or constraints.

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?

The description uses a specific verb ('Returns the list') and resource ('template collaborators'), and it names the key fields included. This makes the tool easy to distinguish from siblings like add_template_collaborator and remove_template_collaborator.

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 implies the tool is for retrieving collaborators on an existing template, but it does not explicitly state when to use it over alternatives or mention exclusions. The use case is reasonably clear for a simple list operation, but no routing guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools