Lovie Company Formation

Create SAFE Envelope

captable_send_safe_for_signature

Destructive

CreateSafeEnvelope opens a two-party SAFE signing envelope from cap-table-supplied data (the caller fetched it via company.GetSafeAgreement): it renders the signable SAFE PDF and inserts the company (order 1) + investor (order 2) signers. The investor's signing link is emailed to them; no tokens are returned to the caller.

Input Schema

TableJSON Schema

Name	Required	Description
`provider`	No
`companyId`	No	UUID value wrapper.
`investors`	No
`companyName`	Yes	Human-readable name (1-255 Unicode chars).
`founderEmail`	No
`valuationCap`	No
`founderUserId`	Yes	UUID value wrapper.
`safeAgreementId`	No
`reminderIntervalDays`	No
`stateOfIncorporation`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`signers`	No
`envelopeId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

removedOutput schema / properties / investorTokens

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

Changed2 schema fields changedSep 10, 2026

removedInput schema / properties / accessCode

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

addedOutput schema / properties / signers / items / properties / dataFields

Added value: +{
+  "items": {
+    "properties": {
+      "box": {
+        "anyOf": [
+          {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "kind": {
+        "enum": [
+          "SIGNER_DATA_FIELD_KIND_UNSPECIFIED",
+          "SIGNER_DATA_FIELD_KIND_NAME",
+          "SIGNER_DATA_FIELD_KIND_TITLE",
+          "SIGNER_DATA_FIELD_KIND_ADDRESS",
+          "SIGNER_DATA_FIELD_KIND_EMAIL",
+          "SIGNER_DATA_FIELD_KIND_DATE"
+        ],
+        "type": "string"
+      },
+      "token": {
+        "type": "string"
+      },
+      "value": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

Changed22 schema fields changedSep 10, 2026
- addedOutput schema / properties / signers / items / properties / actorUserId / anyOf
```
Added value: +[
+  {
+    "description": "UUID value wrapper.",
+    "properties": {
+      "value": {
+        "format": "uuid",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / signers / items / properties / actorUserId / description
```
Removed value: -"UUID value wrapper."
```
- removedOutput schema / properties / signers / items / properties / actorUserId / properties
```
Removed value: -{
-  "value": {
-    "format": "uuid",
-    "type": "string"
-  }
-}
```
- removedOutput schema / properties / signers / items / properties / actorUserId / type
```
Removed value: -"object"
```
- addedOutput schema / properties / signers / items / properties / createdAt / anyOf
```
Added value: +[
+  {
+    "format": "date-time",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / signers / items / properties / createdAt / format
```
Removed value: -"date-time"
```
- removedOutput schema / properties / signers / items / properties / createdAt / type
```
Removed value: -"string"
```
- addedOutput schema / properties / signers / items / properties / inviteEmailedAt / anyOf
```
Added value: +[
+  {
+    "format": "date-time",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / signers / items / properties / inviteEmailedAt / format
```
Removed value: -"date-time"
```
- removedOutput schema / properties / signers / items / properties / inviteEmailedAt / type
```
Removed value: -"string"
```
- removedOutput schema / properties / signers / items / properties / signatureAnchor / additionalProperties
```
Removed value: -true
```
- addedOutput schema / properties / signers / items / properties / signatureAnchor / anyOf
```
Added value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / signers / items / properties / signatureAnchor / type
```
Removed value: -"object"
```
- addedOutput schema / properties / signers / items / properties / signedAt / anyOf
```
Added value: +[
+  {
+    "format": "date-time",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / signers / items / properties / signedAt / format
```
Removed value: -"date-time"
```
- removedOutput schema / properties / signers / items / properties / signedAt / type
```
Removed value: -"string"
```
- addedOutput schema / properties / signers / items / properties / tokenExpiresAt / anyOf
```
Added value: +[
+  {
+    "format": "date-time",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / signers / items / properties / tokenExpiresAt / format
```
Removed value: -"date-time"
```
- removedOutput schema / properties / signers / items / properties / tokenExpiresAt / type
```
Removed value: -"string"
```
- addedOutput schema / properties / signers / items / properties / updatedAt / anyOf
```
Added value: +[
+  {
+    "format": "date-time",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / signers / items / properties / updatedAt / format
```
Removed value: -"date-time"
```
- removedOutput schema / properties / signers / items / properties / updatedAt / type
```
Removed value: -"string"
```

Changed5 schema fields changedAug 17, 2026

addedInput schema / properties / companyId

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

addedInput schema / properties / investors / items / properties / signingOrder

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

addedInput schema / properties / provider

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

addedInput schema / properties / reminderIntervalDays

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

addedOutput schema / properties / signers / items / properties / providerRecipientId
```
Added value: +{
+  "type": "string"
+}
```

First observedAug 11, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations cover the safety profile (destructiveHint=true, openWorldHint=false), and the description adds real behavior beyond them: it renders the PDF, fixes signer order (company 1, investor 2), emails the investor's link, and returns no tokens. It does not explain why the operation is flagged destructive or what state it mutates, so it stops short of 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence that front-loads the core action, then layers in data source, document rendering, signer ordering, and the email side-effect. Efficient with no filler, though a clause or two could be split for scanability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values are covered, and the description usefully notes no tokens are returned. However, for a 10-parameter mutation with nested objects and destructiveHint=true, the description omits what the side effects actually touch and how the optional parameters shape the envelope, leaving meaningful gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 30% across 10 parameters, so the description must compensate and does not. Aside from naming the company/investor signer roles, it is silent on provider, valuationCap, safeAgreementId, reminderIntervalDays, stateOfIncorporation, founderEmail, and the UUID wrappers.

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?

It names a specific verb+resource ('opens a two-party SAFE signing envelope') and scopes it precisely ('from cap-table-supplied data'), which distinguishes it from the generic sibling signature_create_envelope. It even cites the upstream data source (company.GetSafeAgreement), so an agent can place it in a workflow 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 Guidelines3/5

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

Usage is implied by the phrase 'cap-table-supplied data (the caller fetched it via company.GetSafeAgreement)', which signals a prerequisite step, but there is no explicit when-to-use/when-not, and no comparison to signature_create_envelope or the other signature_* siblings. Adequate context, no 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.