Lovie Company Formation

Create Signature Envelope

signature_create_envelope

Open a multi-signer signature envelope over an existing company document. Name the document with source_company_id + source_document_id and the service resolves its storage location and content hash itself - do not supply document_s3_bucket/document_s3_key. Give the founder SIGNER_ROLE_COMPANY at signing_order 1 and each counterparty SIGNER_ROLE_COUNTERPARTY from 2 up. Signing links are emailed to counterparties; no tokens are returned.

Input Schema

TableJSON Schema

Name	Required	Description
`signers`	No
`envelope`	Yes
`documentS3Key`	No
`sourceCompanyId`	No	UUID value wrapper.
`documentS3Bucket`	No
`sourceDocumentId`	No	UUID value wrapper.
`reminderIntervalDays`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`envelopeId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 10, 2026

removedInput schema / properties / accessCode

Removed value: -{
-  "maxLength": 64,
-  "type": "string"
-}

addedInput schema / properties / sourceCompanyId

Added value: +{
+  "description": "UUID value wrapper.",
+  "properties": {
+    "value": {
+      "format": "uuid",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / sourceDocumentId

Added value: +{
+  "description": "UUID value wrapper.",
+  "properties": {
+    "value": {
+      "format": "uuid",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedSep 10, 2026

changedInput schema / properties / signers / items / properties / role / enum

Previous value: -[
-  "SIGNER_ROLE_UNSPECIFIED",
-  "SIGNER_ROLE_COMPANY",
-  "SIGNER_ROLE_INVESTOR",
-  "SIGNER_ROLE_COUNTERPARTY"
-]New value: +[
+  "SIGNER_ROLE_COMPANY",
+  "SIGNER_ROLE_INVESTOR",
+  "SIGNER_ROLE_COUNTERPARTY"
+]

Changed4 schema fields changedAug 17, 2026

addedInput schema / properties / envelope / properties / provider

Added value: +{
+  "enum": [
+    "SIGNATURE_PROVIDER_UNSPECIFIED",
+    "SIGNATURE_PROVIDER_LOVIE_SIGN",
+    "SIGNATURE_PROVIDER_DOCUSIGN"
+  ],
+  "type": "string"
+}

addedInput schema / properties / envelope / properties / providerEnvelopeId
```
Added value: +{
+  "maxLength": 128,
+  "type": "string"
+}
```

addedInput schema / properties / reminderIntervalDays

Added value: +{
+  "maximum": 365,
+  "minimum": 0,
+  "type": "integer"
+}

removedOutput schema / properties / signerTokens

Removed value: -{
-  "items": {
-    "properties": {
-      "rawToken": {
-        "type": "string"
-      },
-      "signerId": {
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}

First observedAug 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only cover openWorldHint=false and destructiveHint=false, so the description usefully adds that the service resolves storage/hash itself, that signing links are emailed to counterparties, and that no tokens are returned. These are non-obvious traits an agent needs. It omits failure modes, idempotency, and permission requirements, keeping it short of a 5.

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?

Four dense sentences, each earning its place, with the core action front-loaded and the parameter conventions following. No filler or restatement of the tool name.

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?

Given an output schema exists, return values need not be explained, and the description covers the primary creation flow and signer layout. Minor gaps remain around reminderIntervalDays and envelope status semantics, but nothing critical to invoking the tool is missing.

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 only 29%, so the description must carry weight, and it does explain source_company_id/source_document_id naming, the signer role convention, and signing_order sequencing. However, other parameters (signer email/anchor/actorUserId, envelope fields, reminderIntervalDays) remain undocumented in both schema and description.

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?

States a specific verb+resource ('Open a multi-signer signature envelope') scoped to an existing company document. This is clearly distinguished from sibling envelope operations like signature_get_signature_envelope, signature_void_envelope, and signature_resend_signer_invite.

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?

Gives clear context (over an existing company document) and an explicit exclusion ('do not supply document_s3_bucket/document_s3_key'), steering the agent to the intended naming path. It does not name an alternative tool or a when-not condition, so it stops short of full routing guidance.

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

All Lovie Company Formation 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.