MCP server providing access to Signaturit API for managing digital signatures and contacts
Signaturit Tools Demo has clear verb-based naming and consistent tool structure, but suffers from incomplete parameter descriptions, missing output schemas, and weak error handling guidance. All 9 tools are explicitly registered with names and basic descriptions in internal/tools files (contact.go, signature.go). However, parameter documentation is inconsistent, many parameters lack detailed format specifications, constraints, or examples of valid values. The create_signature tool's 'recipients' parameter, despite being complex, is described only as 'List of signer objects' with no schema or format guidance. No tool includes documented output schemas, requiring LLMs to infer response structure from code. Error handling returns generic HTTP status messages rather than recovery guidance. The descriptions average ~100 chars, which is brief but acceptable; however, parameter descriptions average ~40 chars and frequently omit constraint details required by the rubric.
Cancel an in-progress signature so it can no longer be signed
Create a new contact in your Signaturit account
Create a new signature request (multi-signer, with optional custom data) using templates instead of file uploads
Delete a contact from your Signaturit account
Get a single contact by ID
Retrieve a single signature request by ID
No output schemas documented for any tool. LLMs cannot predict response structure, forcing trial-and-error parsing. For example, get_contact returns a Contact struct but no schema is visible to the agent.
create_signature's 'recipients' parameter lacks format specification. Description says 'List of signer objects, each with name, email (or phone if SMS)...' but no schema, JSON example, or parsing rules are provided. LLM cannot construct valid input.
Parameter descriptions lack constraint details. Examples: 'contact_id' (required) has no format example or UUID pattern; 'expires_in_days' (number, optional) has no min/max bounds stated; 'signing_mode' should be an enum but is described as free-form string.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 53 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 44 | - | v1 |
Get all contacts from your Signaturit account
Send a reminder email/SMS to the signer of a pending signature
Update an existing contact's information
Error responses in handlers (internal/handlers/contact.go) return raw HTTP status codes and API body text, e.g., 'unexpected status code: 400, body: {...}'. LLMs receive no guidance on what went wrong, how to fix it, or which tool to call next.
No pagination support documented for list_contacts, which may return unbounded results. Rubric requires page/offset, limit, and total_count to prevent context window exhaustion.
Destructive tools (delete_contact, cancel_signature) lack dry-run or confirmation step. No confirmation_request or input_required pattern prevents accidental deletion.
Tool descriptions do not state whether they modify state. Agents need explicit documentation of which calls are safe to retry and which have irreversible consequences.