Skip to main content
Glama

anvil

by io.usefulapi

Create Etch e-signature packet

anvil_create_etch_packet
Destructive

Create an Etch e-signature packet (documents + signers). GraphQL mutation: createEtchPacket. IMPORTANT: isDraft defaults to true (a safe draft that sends nothing). Setting isDraft=false with real signers SENDS signature-request emails to those signers. Use isTest=true while developing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoOptional payload data used to pre-fill the packet's documents.
nameYesHuman-readable name for the packet.
filesNoArray of file/document objects (casts or uploads) to include. Passed straight through to Anvil.
isTestNoSet true to create a test packet (no legal weight, no charge).
isDraftNoDefault true. When true, creates a draft and sends nothing. Set false to activate and email signers.
signersNoArray of signer objects, e.g. [{ id, name, email, signerType, routingOrder, fields }]. Passed straight through to Anvil.
signatureEmailBodyNoOptional body text for the signature-request email.
signatureEmailSubjectNoOptional subject line for the signature-request email.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds context beyond destructiveHint: describes mutation, default draft behavior, email sending, and test mode. Does not contradict annotations.

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 efficient sentences: purpose, critical default behavior, and test mode advice. Front-loaded with important warnings.

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?

Covers creation, email side effects, and test/non-test usage. Missing description of return value (no output schema) but otherwise complete for a create tool with 8 params.

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%, so baseline is 3. Description adds minimal extra meaning beyond schema, e.g., 'passed straight through to Anvil' for files and signers.

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?

Clearly states it creates an Etch e-signature packet with documents and signers. Distinguishes from sibling tools like anvil_get_etch_packet (retrieve) and anvil_generate_etch_sign_url (generate URL).

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?

Explicitly warns about isDraft defaulting to true and that setting it to false sends emails. Recommends using isTest=true during development. Provides context for safe usage.

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

All anvil toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation5/5

Each tool targets a distinct function: user info, PDF creation/filling, e-signature management, and workflow queries. No two tools have overlapping purposes; even the two PDF tools (fill_pdf vs generate_pdf) are clearly separated by input type.

Naming Consistency5/5

All tools use the 'anvil_' prefix followed by verb_noun in snake_case (e.g., create_etch_packet, get_cast). The pattern is perfectly consistent across all 10 tools.

Tool Count5/5

10 tools cover the major Anvil capabilities (PDF, e-sign, organization, workflows) without unnecessary redundancy. The count is well-scoped for the server's purpose.

Completeness3/5

The set lacks list/update/delete operations for several resources (e.g., no list_casts, no update_etch_packet). While key create and get operations are present, agents may need to work around missing CRUD coverage.

Resources