Lovie Company Formation

Get OCR Upload URL

formation_get_ocr_upload_url

Read-only

Returns a presigned S3 PUT URL for uploading a company document (kind=SAFE for a SAFE PDF, kind=RSA for a signed restricted stock purchase agreement, kind=CAP_TABLE for a cap-table file, kind=WIRE_PROOF for a wire payment proof). Step 1 of every document-import flow: call with the matching kind and mime_type=application/pdf, upload the file bytes to the returned upload_url with an HTTP PUT, then pass the returned source_s3_uri to the next step — ImportSAFE for a SAFE, ExtractRsaTermsOcr (then CreateCapTableAgreement with type=RSA) for a signed RSA, or ExtractCapTableOcr for a cap table. Company-scoped — no formation record needed.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`expiresAt`	No
`uploadUrl`	No
`sourceS3Uri`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026

changedInput schema / properties / kind / enum

Previous value: -[
-  "FORMATION_UPLOAD_KIND_CAP_TABLE",
-  "FORMATION_UPLOAD_KIND_SAFE",
-  "FORMATION_UPLOAD_KIND_RSA",
-  "FORMATION_UPLOAD_KIND_WIRE_PROOF",
-  "FORMATION_UPLOAD_KIND_EIN_DOCUMENT",
-  "FORMATION_UPLOAD_KIND_DOCUMENT"
-]New value: +[
+  "FORMATION_UPLOAD_KIND_CAP_TABLE",
+  "FORMATION_UPLOAD_KIND_SAFE",
+  "FORMATION_UPLOAD_KIND_RSA",
+  "FORMATION_UPLOAD_KIND_WIRE_PROOF",
+  "FORMATION_UPLOAD_KIND_EIN_DOCUMENT",
+  "FORMATION_UPLOAD_KIND_DOCUMENT",
+  "FORMATION_UPLOAD_KIND_FAST"
+]

Changed4 schema fields changedSep 10, 2026

changedInput schema / properties / kind / enum

Previous value: -[
-  "FORMATION_UPLOAD_KIND_UNSPECIFIED",
-  "FORMATION_UPLOAD_KIND_CAP_TABLE",
-  "FORMATION_UPLOAD_KIND_SAFE",
-  "FORMATION_UPLOAD_KIND_RSA",
-  "FORMATION_UPLOAD_KIND_WIRE_PROOF",
-  "FORMATION_UPLOAD_KIND_EIN_DOCUMENT",
-  "FORMATION_UPLOAD_KIND_DOCUMENT"
-]New value: +[
+  "FORMATION_UPLOAD_KIND_CAP_TABLE",
+  "FORMATION_UPLOAD_KIND_SAFE",
+  "FORMATION_UPLOAD_KIND_RSA",
+  "FORMATION_UPLOAD_KIND_WIRE_PROOF",
+  "FORMATION_UPLOAD_KIND_EIN_DOCUMENT",
+  "FORMATION_UPLOAD_KIND_DOCUMENT"
+]

addedOutput schema / properties / expiresAt / anyOf

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

removedOutput schema / properties / expiresAt / format
```
Removed value: -"date-time"
```
removedOutput schema / properties / expiresAt / type
```
Removed value: -"string"
```

First observedAug 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds important operational behavior: the client must HTTP PUT file bytes to the returned upload_url and use source_s3_uri downstream. It does not mention URL expiration or auth requirements.

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 tool's purpose. The paragraph is dense but every clause (kind mapping, upload step, downstream routing) carries useful flow information. It could be split for readability, but there is no filler.

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?

Because an output schema exists, the description need not explain return values, and annotations cover the safety profile. It covers the import flow and downstream branches well, but leaves gaps on full enum coverage and mimeType alternatives. Adequate for a step-1 helper tool.

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 only 33%, so the description must compensate. It maps several kind enum values (SAFE, RSA, CAP_TABLE, WIRE_PROOF) and specifies mime_type=application/pdf, but omits EIN_DOCUMENT, DOCUMENT, and FAST, does not explain the required companyId parameter, and its blanket application/pdf guidance is narrower than the schema's mimeType pattern.

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 and resource: returns a presigned S3 PUT URL for uploading a company document. It names the relevant kinds and downstream OCR import tools, clearly distinguishing it from sibling upload helpers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly says 'Step 1 of every document-import flow', specifies calling with the matching kind and mime_type, then uploading bytes and passing source_s3_uri to the correct next tool. It routes to ImportSAFE, ExtractRsaTermsOcr, or ExtractCapTableOcr based on kind.

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.