Formify — AI Assisted E-Signing

Duplicate Template

duplicate_template

Copy a template, leaving the original untouched. The copy belongs to whoever duplicated it, so this is also how you take your own private copy of a template a colleague shared with the account. Duplicating a template is free — unlike duplicating a public link.

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": {
      "templateId": "<templateId>"
    },
    "name": "duplicate_template"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	Name for the copy. Defaults to the source's name, which leaves you with two templates of the same name — usually worth setting.
`templateId`	Yes	Unique identifier of the template to copy

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate this is a non-read-only, non-destructive, non-idempotent mutation. The description adds important behavior beyond the annotations: the original is untouched, ownership of the copy transfers to the duplicator, and there is no cost. It does not mention that repeated calls create separate copies, which would have been useful given idempotentHint=false.

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 the core copy behavior and followed by ownership and cost details that directly affect tool selection. There is no repetition or wasted text.

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 two-parameter duplicate operation with annotations covering the safety profile, the description explains the key behavioral context: original preservation, copy ownership, and cost. It does not describe what the tool returns, though no output schema exists, leaving a minor 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 description coverage is 100%, and the schema already explains both templateId and name, including the default naming behavior. The description adds no parameter-level information beyond what the schema provides, so the baseline 3 is appropriate.

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 and resource: copy a template while leaving the original untouched. It also distinguishes the operation from creating from scratch and from duplicating a public link, so an agent can identify it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context: use this to make a private copy of a template shared by a colleague, and notes that duplication is free unlike duplicating a public link. It does not explicitly state when not to use it or name create_template as an alternative, so it falls short of a 5.

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

All Formify — AI Assisted E-Signing tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?