Lovie Company Formation

Extract Cap Table OCR

formation_extract_cap_table_ocr

Runs vision OCR on an uploaded cap table for the active company and returns the extracted rows without persisting them. Each row may include a vesting schedule (vesting_start_date / vesting_total_months / vesting_cliff_months) for service equity held by founders, employees, and advisors. PRESERVE these vesting fields and pass them through to RecordCapTableInvestment when creating each holding — do not drop them or record such holdings as fully vested. Investor instruments (SAFE, preferred) carry no vesting.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "companyId": "<companyId>"
    },
    "name": "formation_extract_cap_table_ocr"
  }
}

Input Schema

Name	Required	Description
`mimeType`	No
`companyId`	Yes	UUID value wrapper.
`sourceS3Uri`	No

Output Schema

Name	Required	Description	Default
`warnings`	No
`sourceS3Uri`	No
`totalShares`	No
`ocrConfidence`	No
`sourceTotalShares`	No
`extractedShareholders`	No
`safeOwnershipPercentage`	No
`totalOwnershipPercentage`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 8, 2026

changedOutput schema / properties / extractedShareholders / items / properties / safeTerms / anyOf

Previous value: -[
-  {
-    "properties": {
-      "discountPercentage": {
-        "type": "string"
-      },
-      "investmentAmountCents": {
-        "type": "string"
-      },
-      "postMoney": {
-        "type": "boolean"
-      },
-      "safeIssueDate": {
-        "anyOf": [
-          {
-            "format": "date-time",
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "signedByName": {
-        "type": "string"
-      },
-      "signedByTitle": {
-        "type": "string"
-      },
-      "valuationCapCents": {
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "discountPercentage": {
+        "type": "string"
+      },
+      "investmentAmountCents": {
+        "type": "string"
+      },
+      "postMoney": {
+        "type": "boolean"
+      },
+      "postMoneyStated": {
+        "type": "boolean"
+      },
+      "safeIssueDate": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "signedByName": {
+        "type": "string"
+      },
+      "signedByTitle": {
+        "type": "string"
+      },
+      "valuationCapCents": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

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

Changed26 schema fields changedSep 10, 2026

addedOutput schema / properties / extractedShareholders / items / properties / address / anyOf

Added value: +[
+  {
+    "properties": {
+      "city": {
+        "type": "string"
+      },
+      "country": {
+        "type": "string"
+      },
+      "county": {
+        "type": "string"
+      },
+      "state": {
+        "type": "string"
+      },
+      "street1": {
+        "type": "string"
+      },
+      "street2": {
+        "type": "string"
+      },
+      "zipCode": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / extractedShareholders / items / properties / address / properties

Removed value: -{
-  "city": {
-    "type": "string"
-  },
-  "country": {
-    "type": "string"
-  },
-  "county": {
-    "type": "string"
-  },
-  "state": {
-    "type": "string"
-  },
-  "street1": {
-    "type": "string"
-  },
-  "street2": {
-    "type": "string"
-  },
-  "zipCode": {
-    "type": "string"
-  }
-}

removedOutput schema / properties / extractedShareholders / items / properties / address / type
```
Removed value: -"object"
```

addedOutput schema / properties / extractedShareholders / items / properties / addressType

Added value: +{
+  "enum": [
+    "ADDRESS_TYPE_UNSPECIFIED",
+    "ADDRESS_TYPE_RESIDENTIAL",
+    "ADDRESS_TYPE_BUSINESS"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / extractedShareholders / items / properties / dateOfBirth
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / extractedShareholders / items / properties / effectiveDate / anyOf

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

removedOutput schema / properties / extractedShareholders / items / properties / effectiveDate / format
```
Removed value: -"date-time"
```
removedOutput schema / properties / extractedShareholders / items / properties / effectiveDate / type
```
Removed value: -"string"
```

addedOutput schema / properties / extractedShareholders / items / properties / id / anyOf

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

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

addedOutput schema / properties / extractedShareholders / items / properties / issueDate / anyOf

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

removedOutput schema / properties / extractedShareholders / items / properties / issueDate / format
```
Removed value: -"date-time"
```
removedOutput schema / properties / extractedShareholders / items / properties / issueDate / type
```
Removed value: -"string"
```

addedOutput schema / properties / extractedShareholders / items / properties / safeTerms / anyOf

Added value: +[
+  {
+    "properties": {
+      "discountPercentage": {
+        "type": "string"
+      },
+      "investmentAmountCents": {
+        "type": "string"
+      },
+      "postMoney": {
+        "type": "boolean"
+      },
+      "safeIssueDate": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "signedByName": {
+        "type": "string"
+      },
+      "signedByTitle": {
+        "type": "string"
+      },
+      "valuationCapCents": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / extractedShareholders / items / properties / safeTerms / properties

Removed value: -{
-  "discountPercentage": {
-    "type": "string"
-  },
-  "investmentAmountCents": {
-    "type": "string"
-  },
-  "postMoney": {
-    "type": "boolean"
-  },
-  "safeIssueDate": {
-    "format": "date-time",
-    "type": "string"
-  },
-  "signedByName": {
-    "type": "string"
-  },
-  "signedByTitle": {
-    "type": "string"
-  },
-  "valuationCapCents": {
-    "type": "string"
-  }
-}

removedOutput schema / properties / extractedShareholders / items / properties / safeTerms / type
```
Removed value: -"object"
```

addedOutput schema / properties / extractedShareholders / items / properties / signedDate / anyOf

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

removedOutput schema / properties / extractedShareholders / items / properties / signedDate / format
```
Removed value: -"date-time"
```
removedOutput schema / properties / extractedShareholders / items / properties / signedDate / type
```
Removed value: -"string"
```
addedOutput schema / properties / extractedShareholders / items / properties / ssnLast4
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / extractedShareholders / items / properties / vestingStartDate / anyOf

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

removedOutput schema / properties / extractedShareholders / items / properties / vestingStartDate / format
```
Removed value: -"date-time"
```
removedOutput schema / properties / extractedShareholders / items / properties / vestingStartDate / type
```
Removed value: -"string"
```
addedOutput schema / properties / sourceTotalShares
```
Added value: +{
+  "type": "string"
+}
```

First observedAug 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructiveHint=false and openWorldHint=false, so safety is partly covered, but the description adds real context beyond them: it explicitly states results are not persisted, and it warns that vesting fields must be preserved and holdings must not be flattened to fully-vested. That is a genuine downstream behavioral constraint the annotations do not carry.

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?

Front-loaded with the core action and non-persistence in the first sentence, and the vesting caveat is high-value rather than filler. It runs a little long with the parenthetical field names, but every clause carries actionable information.

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?

An output schema exists so return-shape explanation is not required, and the description instead covers the important semantic content of rows (vesting fields, instrument types) plus the non-persistence contract. The main remaining gap is that the input parameters are barely addressed, which is partly excused by the schema's regex constraints.

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 33% (only companyId carries a wrapper note; mimeType and sourceS3Uri are undocumented), and the description says nothing about any parameter, its format, or the S3 URI requirement. With low coverage the description should compensate but instead leaves two of three parameters explained only by regex patterns.

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 (runs vision OCR) and resource (uploaded cap table) and distinguishes itself from same-family OCR siblings like extract_safe_terms_ocr / extract_rsa_terms_ocr by naming the artifact it handles. The scope ('for the active company', 'without persisting') lets an agent tell it apart from formation_extract_cap_table and the recording tools without opening any 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?

It implies the usage pattern by describing downstream hand-off to RecordCapTableInvestment and stating it does not persist, but it never explicitly says when to prefer this over formation_extract_cap_table or the other extraction tools, nor does it give prerequisites. Usage is inferable rather than stated.

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.