MCP server for eSignatures (https://esignatures.com)
Server has 13 tools with explicit schemas and descriptions, but quality is inconsistent. Naming follows verb_noun convention well (create_contract, query_template, etc.). However, descriptions vary widely in detail and actionability. Many parameter descriptions are present but lack specificity on constraints, formats, and valid ranges. Schemas are visible but incomplete, several parameters lack type definitions or descriptions. Error handling is minimal; responses are raw API JSON without recovery guidance. No tool annotations (readOnlyHint, destructiveHint) despite clear risk levels. Output schemas are not documented. The create_contract tool has a complex nested schema but lacks clarity on mutually exclusive parameters and dependencies.
Creates a HTTPS link for editing a contract template; sends an invitation email if an email is provided..
Creates a new contract. The contract can be a draft which the user can customize/send, or the contract can be sent instantly. So called 'signature fields' like Name/Date/signature-line must be left out, they are all handled automatically. Contract owners can customize the content by replacing {{placeholder fields}} inside the content, and the signers can fill in Signer fields when they sign the contract.
Creates a reusable contract template for contracts to be based on.
Deletes a contract. The contract can only be deleted if it's a test contract or a draft contract.
Deletes a contract template.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels. delete_contract and delete_template are destructive but unmarked; query_contract and list_templates are read-only but unmarked. LLMs cannot distinguish safe from dangerous operations.
Output schemas are not documented. Tools return raw API responses (status_code + JSON) without specifying what fields the LLM should expect. Agents cannot plan downstream calls or extract required IDs.
Error handling is minimal. Responses are raw HTTP status codes and API JSON. No recovery guidance (e.g., 'User not found. Try search_users() first'). LLMs cannot self-correct or retry intelligently.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 52 | 2026-07-28+ | v2 |
Returns the the details of the latest 100 contracts.
Returns the list of template collaborators, including their GUID, name, email, and the HTTPS link for editing the template
Lists the templates.
Responds with the contract details, contract_id, status, final PDF url if present, title, labels, metadata, expiry time if present, and signer details with all signer events (signer events are included only for recent contracts, with rate limiting).
Responds with the template details, template_id, title, labels, created_at, list of the Placeholder fields in the template, list of Signer fields int he template, and the full content inside document_elements
Removes the template collaborator
Updates the title, labels or the content of a contract template.
Withdraws a sent contract.
Parameter descriptions lack specificity on constraints and formats. E.g., 'expires_in_hours' has no min/max; 'locale' enum is present but other string params lack format guidance. LLMs will pass invalid values.
Mutually exclusive parameters not documented. create_contract accepts both 'template_id' and 'document_elements' but does not state which is required or how they interact. LLMs will guess and pass both or neither.