Lovie Company Formation

Get Signature Envelope

signature_get_signature_envelope

Read-only

Returns one signature envelope by id: the documents in it, every signer, and who has signed so far. Read-only. Use this to answer "who still needs to sign" for a specific envelope.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`envelopeId`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`events`	No
`envelope`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedSep 10, 2026

addedOutput schema / properties / envelope / anyOf

Added value: +[
+  {
+    "properties": {
+      "certificateSha256": {
+        "type": "string"
+      },
+      "completedAt": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "consentVersionId": {
+        "type": "string"
+      },
+      "createdAt": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "documentSha256": {
+        "type": "string"
+      },
+      "envelopeType": {
+        "type": "string"
+      },
+      "finalArtifactSha256": {
+        "type": "string"
+      },
+      "id": {
+        "type": "string"
+      },
+      "provider": {
+        "enum": [
+          "SIGNATURE_PROVIDER_UNSPECIFIED",
+          "SIGNATURE_PROVIDER_LOVIE_SIGN",
+          "SIGNATURE_PROVIDER_DOCUSIGN"
+        ],
+        "type": "string"
+      },
+      "providerEnvelopeId": {
+        "type": "string"
+      },
+      "signedDocumentSha256": {
+        "type": "string"
+      },
+      "status": {
+        "enum": [
+          "SIGNATURE_ENVELOPE_STATUS_UNSPECIFIED",
+          "SIGNATURE_ENVELOPE_STATUS_CREATED",
+          "SIGNATURE_ENVELOPE_STATUS_SENT",
+          "SIGNATURE_ENVELOPE_STATUS_VIEWED",
+          "SIGNATURE_ENVELOPE_STATUS_CONSENTED",
+          "SIGNATURE_ENVELOPE_STATUS_SIGNED",
+          "SIGNATURE_ENVELOPE_STATUS_COMPLETED",
+          "SIGNATURE_ENVELOPE_STATUS_VOIDED"
+        ],
+        "type": "string"
+      },
+      "subjectRef": {
+        "anyOf": [
+          {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "userId": {
+        "anyOf": [
+          {
+            "description": "UUID value wrapper.",
+            "properties": {
+              "value": {
+                "format": "uuid",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "voidedAt": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / envelope / properties

Removed value: -{
-  "certificateSha256": {
-    "type": "string"
-  },
-  "completedAt": {
-    "format": "date-time",
-    "type": "string"
-  },
-  "consentVersionId": {
-    "type": "string"
-  },
-  "createdAt": {
-    "format": "date-time",
-    "type": "string"
-  },
-  "documentSha256": {
-    "type": "string"
-  },
-  "envelopeType": {
-    "type": "string"
-  },
-  "finalArtifactSha256": {
-    "type": "string"
-  },
-  "id": {
-    "type": "string"
-  },
-  "provider": {
-    "enum": [
-      "SIGNATURE_PROVIDER_UNSPECIFIED",
-      "SIGNATURE_PROVIDER_LOVIE_SIGN",
-      "SIGNATURE_PROVIDER_DOCUSIGN"
-    ],
-    "type": "string"
-  },
-  "providerEnvelopeId": {
-    "type": "string"
-  },
-  "signedDocumentSha256": {
-    "type": "string"
-  },
-  "status": {
-    "enum": [
-      "SIGNATURE_ENVELOPE_STATUS_UNSPECIFIED",
-      "SIGNATURE_ENVELOPE_STATUS_CREATED",
-      "SIGNATURE_ENVELOPE_STATUS_SENT",
-      "SIGNATURE_ENVELOPE_STATUS_VIEWED",
-      "SIGNATURE_ENVELOPE_STATUS_CONSENTED",
-      "SIGNATURE_ENVELOPE_STATUS_SIGNED",
-      "SIGNATURE_ENVELOPE_STATUS_COMPLETED",
-      "SIGNATURE_ENVELOPE_STATUS_VOIDED"
-    ],
-    "type": "string"
-  },
-  "subjectRef": {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  "userId": {
-    "description": "UUID value wrapper.",
-    "properties": {
-      "value": {
-        "format": "uuid",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "voidedAt": {
-    "format": "date-time",
-    "type": "string"
-  }
-}

removedOutput schema / properties / envelope / type
```
Removed value: -"object"
```

addedOutput schema / properties / events / items / properties / actorUserId / anyOf

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

removedOutput schema / properties / events / items / properties / actorUserId / description
```
Removed value: -"UUID value wrapper."
```
removedOutput schema / properties / events / items / properties / actorUserId / properties
```
Removed value: -{
-  "value": {
-    "format": "uuid",
-    "type": "string"
-  }
-}
```
removedOutput schema / properties / events / items / properties / actorUserId / type
```
Removed value: -"object"
```

addedOutput schema / properties / events / items / properties / createdAt / anyOf

Added value: +[
+  {
+    "format": "date-time",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / events / items / properties / createdAt / format
```
Removed value: -"date-time"
```
removedOutput schema / properties / events / items / properties / createdAt / type
```
Removed value: -"string"
```
removedOutput schema / properties / events / items / properties / metadata / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties / events / items / properties / metadata / anyOf

Added value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / events / items / properties / metadata / type
```
Removed value: -"object"
```

Changed2 schema fields changedAug 17, 2026

addedOutput schema / properties / envelope / properties / provider

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

addedOutput schema / properties / envelope / properties / providerEnvelopeId
```
Added value: +{
+  "type": "string"
+}
```

First observedAug 11, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description restates 'Read-only' but adds useful behavior by saying what the returned envelope contains (documents, signers, and signing status). It does not go deeper into error behavior or auth expectations, but with annotations covering the safety profile this is adequate.

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?

Two short sentences, front-loaded with the action and resource, followed by a practical use case. 'Read-only' slightly duplicates the annotation, but it is still a natural and useful in-description reminder.

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?

For a simple one-parameter read tool with an output schema present, the description is nearly complete: it states the purpose, the returned contents, and the intended question it answers. The only small gap is not making the required-ness of envelopeId explicit.

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 description coverage is 0%, so the description must compensate. 'by id' tells the agent that envelopeId is the identifier, but it does not explicitly confirm that envelopeId is required or explain the format beyond the schema's min/max. This is enough to use the tool, but not fully detailed.

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?

The description uses a specific verb ('Returns one signature envelope by id') and clearly identifies the resource and the included details: documents, signers, and signing progress. It also names a concrete query use case ('who still needs to sign'), making it easy to distinguish from list/status siblings.

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?

The description gives an explicit use case: answering 'who still needs to sign' for a specific envelope. It implies this is the single-envelope lookup tool rather than the list variant, though it does not explicitly name alternative tools or exclusion conditions.

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.