Lovie Company Formation

List Signature Envelopes

signature_get_list_signature_envelopes

Read-only

Lists a company's signature envelopes with their status and signer progress. Read-only and paginated. Use this to answer "what is out for signature" or to find an envelope id.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`filter`	No
`pageSize`	No
`pageToken`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`envelopes`	No
`totalCount`	No
`nextPageToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedSep 10, 2026
- addedOutput schema / properties / envelopes / items / properties / completedAt / anyOf
```
Added value: +[
+  {
+    "format": "date-time",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / envelopes / items / properties / completedAt / format
```
Removed value: -"date-time"
```
- removedOutput schema / properties / envelopes / items / properties / completedAt / type
```
Removed value: -"string"
```
- addedOutput schema / properties / envelopes / items / properties / createdAt / anyOf
```
Added value: +[
+  {
+    "format": "date-time",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / envelopes / items / properties / createdAt / format
```
Removed value: -"date-time"
```
- removedOutput schema / properties / envelopes / items / properties / createdAt / type
```
Removed value: -"string"
```
- removedOutput schema / properties / envelopes / items / properties / subjectRef / additionalProperties
```
Removed value: -true
```
- addedOutput schema / properties / envelopes / items / properties / subjectRef / anyOf
```
Added value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / envelopes / items / properties / subjectRef / type
```
Removed value: -"object"
```
- addedOutput schema / properties / envelopes / items / properties / userId / anyOf
```
Added value: +[
+  {
+    "description": "UUID value wrapper.",
+    "properties": {
+      "value": {
+        "format": "uuid",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / envelopes / items / properties / userId / description
```
Removed value: -"UUID value wrapper."
```
- removedOutput schema / properties / envelopes / items / properties / userId / properties
```
Removed value: -{
-  "value": {
-    "format": "uuid",
-    "type": "string"
-  }
-}
```
- removedOutput schema / properties / envelopes / items / properties / userId / type
```
Removed value: -"object"
```
- addedOutput schema / properties / envelopes / items / properties / voidedAt / anyOf
```
Added value: +[
+  {
+    "format": "date-time",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / envelopes / items / properties / voidedAt / format
```
Removed value: -"date-time"
```
- removedOutput schema / properties / envelopes / items / properties / voidedAt / type
```
Removed value: -"string"
```

Changed2 schema fields changedAug 17, 2026

addedOutput schema / properties / envelopes / items / properties / provider

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

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

First observedAug 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful context beyond the annotations by explicitly saying the operation is paginated and that results include status and signer progress. No contradictions with annotations.

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?

The description is three short sentences with no fluff. It front-loads the core purpose, adds the read-only and pagination traits, and ends with practical use cases. Every sentence earns its place.

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?

Given the nested filter schema and three parameters, the description is too minimal to be fully contextually complete. The output schema covers return values, and annotations cover safety, but filter semantics and pagination mechanics are left unexplained, leaving an agent unable to fully understand how to narrow results.

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 0%, so the description must compensate for undocumented parameters. It only implies pagination through the word 'paginated' and does not explain the filter object, statuses, envelopeType, pageSize, or pageToken. This is insufficient for an agent to know how to construct a query.

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 states a specific verb-resource pairing: 'Lists a company's signature envelopes' and adds what the list includes (status and signer progress). It also names concrete use cases ('what is out for signature', 'find an envelope id') that clearly distinguish it from the singular sibling signature_get_signature_envelope.

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 explicit use cases: answering what is out for signature and finding an envelope ID. It does not explicitly mention when not to use it or name alternatives, but the usage guidance is clear enough for an agent to select this list tool over a get tool.

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.