Lovie Company Formation

List Saved Signatures

documents_list_saved_signatures

Read-only

List the caller's saved signatures for the selected company.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`companyId`	Yes	UUID value wrapper.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`savedSignatures`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedSep 10, 2026
- addedOutput schema / properties / savedSignatures / items / properties / companyId / anyOf
```
Added value: +[
+  {
+    "description": "UUID value wrapper.",
+    "properties": {
+      "value": {
+        "format": "uuid",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / savedSignatures / items / properties / companyId / description
```
Removed value: -"UUID value wrapper."
```
- removedOutput schema / properties / savedSignatures / items / properties / companyId / properties
```
Removed value: -{
-  "value": {
-    "format": "uuid",
-    "type": "string"
-  }
-}
```
- removedOutput schema / properties / savedSignatures / items / properties / companyId / type
```
Removed value: -"object"
```
- addedOutput schema / properties / savedSignatures / items / properties / createdAt / anyOf
```
Added value: +[
+  {
+    "format": "date-time",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / savedSignatures / items / properties / createdAt / format
```
Removed value: -"date-time"
```
- removedOutput schema / properties / savedSignatures / items / properties / createdAt / type
```
Removed value: -"string"
```
- addedOutput schema / properties / savedSignatures / items / properties / documentId / anyOf
```
Added value: +[
+  {
+    "description": "UUID value wrapper.",
+    "properties": {
+      "value": {
+        "format": "uuid",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / savedSignatures / items / properties / documentId / description
```
Removed value: -"UUID value wrapper."
```
- removedOutput schema / properties / savedSignatures / items / properties / documentId / properties
```
Removed value: -{
-  "value": {
-    "format": "uuid",
-    "type": "string"
-  }
-}
```
- removedOutput schema / properties / savedSignatures / items / properties / documentId / type
```
Removed value: -"object"
```
- addedOutput schema / properties / savedSignatures / items / properties / id / anyOf
```
Added value: +[
+  {
+    "description": "UUID value wrapper.",
+    "properties": {
+      "value": {
+        "format": "uuid",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / savedSignatures / items / properties / id / description
```
Removed value: -"UUID value wrapper."
```
- removedOutput schema / properties / savedSignatures / items / properties / id / properties
```
Removed value: -{
-  "value": {
-    "format": "uuid",
-    "type": "string"
-  }
-}
```
- removedOutput schema / properties / savedSignatures / items / properties / id / type
```
Removed value: -"object"
```
- addedOutput schema / properties / savedSignatures / items / properties / userId / anyOf
```
Added value: +[
+  {
+    "description": "UUID value wrapper.",
+    "properties": {
+      "value": {
+        "format": "uuid",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / savedSignatures / items / properties / userId / description
```
Removed value: -"UUID value wrapper."
```
- removedOutput schema / properties / savedSignatures / items / properties / userId / properties
```
Removed value: -{
-  "value": {
-    "format": "uuid",
-    "type": "string"
-  }
-}
```
- removedOutput schema / properties / savedSignatures / items / properties / userId / type
```
Removed value: -"object"
```
First observedAug 11, 2026

TDQS

A4.3/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, so the safety profile is established. The description adds useful scoping: it returns only the caller's own signatures for the given company. However, it does not disclose details like pagination or return format, which are partially covered by the output schema. Thus it adds some context but not extensive behavioral depth.

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 a single, front-loaded sentence with no extraneous information. It conveys the action, resource, and scope efficiently, earning every word.

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

Completeness5/5

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

For a read-only list tool with one parameter, readOnlyHint/destructiveHint annotations, and an output schema, the description covers all essential aspects: what it does, who it applies to (caller), and the company scope. Nothing critical is missing, making it complete for correct invocation.

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

Parameters4/5

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

The input schema describes companyId merely as a 'UUID value wrapper', which lacks semantic meaning. The description clarifies that the parameter selects the company for which signatures are listed, adding meaning beyond the schema. Since schema coverage is 100% but the description enriches the parameter's purpose, a score of 4 is appropriate.

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 ('List') and resource ('the caller's saved signatures'), scoped to a selected company. This clearly distinguishes it from broader document tools and signature envelope tools among siblings, so an agent can identify its function precisely.

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 provides clear context: it lists saved signatures for a specific company, implying the need for a companyId. It does not explicitly mention alternatives or when not to use it, but the context is unambiguous, and there are no misleading exclusions.

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.