Lovie Company Formation

Reopen Cap Table Round

cap_table_reopen_cap_table_round

Destructive

ReopenCapTableRound flips a CLOSED round back to OPEN (status only).

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`round`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 10, 2026

addedOutput schema / properties / round / anyOf

Added value: +[
+  {
+    "properties": {
+      "closedAt": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "companyId": {
+        "anyOf": [
+          {
+            "description": "UUID value wrapper.",
+            "properties": {
+              "value": {
+                "format": "uuid",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "createdAt": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "fullyDilutedShares": {
+        "type": "string"
+      },
+      "id": {
+        "anyOf": [
+          {
+            "description": "UUID value wrapper.",
+            "properties": {
+              "value": {
+                "format": "uuid",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "isPriced": {
+        "type": "boolean"
+      },
+      "name": {
+        "type": "string"
+      },
+      "optionPoolPct": {
+        "type": "string"
+      },
+      "optionPoolShares": {
+        "type": "string"
+      },
+      "postMoneyValuation": {
+        "type": "string"
+      },
+      "preMoneyValuation": {
+        "type": "string"
+      },
+      "pricePerShare": {
+        "type": "string"
+      },
+      "status": {
+        "enum": [
+          "CAP_TABLE_ROUND_STATUS_UNSPECIFIED",
+          "CAP_TABLE_ROUND_STATUS_OPEN",
+          "CAP_TABLE_ROUND_STATUS_CLOSING",
+          "CAP_TABLE_ROUND_STATUS_CLOSED"
+        ],
+        "type": "string"
+      },
+      "totalRaiseTarget": {
+        "type": "string"
+      },
+      "updatedAt": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "required": [
+      "companyId"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / round / properties

Removed value: -{
-  "closedAt": {
-    "format": "date-time",
-    "type": "string"
-  },
-  "companyId": {
-    "description": "UUID value wrapper.",
-    "properties": {
-      "value": {
-        "format": "uuid",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "createdAt": {
-    "format": "date-time",
-    "type": "string"
-  },
-  "fullyDilutedShares": {
-    "type": "string"
-  },
-  "id": {
-    "description": "UUID value wrapper.",
-    "properties": {
-      "value": {
-        "format": "uuid",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "isPriced": {
-    "type": "boolean"
-  },
-  "name": {
-    "type": "string"
-  },
-  "optionPoolPct": {
-    "type": "string"
-  },
-  "optionPoolShares": {
-    "type": "string"
-  },
-  "postMoneyValuation": {
-    "type": "string"
-  },
-  "preMoneyValuation": {
-    "type": "string"
-  },
-  "pricePerShare": {
-    "type": "string"
-  },
-  "status": {
-    "enum": [
-      "CAP_TABLE_ROUND_STATUS_UNSPECIFIED",
-      "CAP_TABLE_ROUND_STATUS_OPEN",
-      "CAP_TABLE_ROUND_STATUS_CLOSING",
-      "CAP_TABLE_ROUND_STATUS_CLOSED"
-    ],
-    "type": "string"
-  },
-  "totalRaiseTarget": {
-    "type": "string"
-  },
-  "updatedAt": {
-    "format": "date-time",
-    "type": "string"
-  }
-}

removedOutput schema / properties / round / required
```
Removed value: -[
-  "companyId"
-]
```
removedOutput schema / properties / round / type
```
Removed value: -"object"
```

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 mark this as destructive, and the description adds valuable context by specifying the exact behavioral scope: only the status is changed, no other round data is affected. This helps an agent understand the blast radius beyond the generic destructiveHint.

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?

A single sentence delivers the core purpose, the state transition, and the scope limitation. Every word earns its place; there is no redundancy or filler.

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 single-parameter status-transition tool, the description plus annotations and output schema provide everything an agent needs. The state prerequisite (round must be CLOSED) is stated, and the mutation scope is clarified.

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?

The schema covers 100% of the parameter documentation, including the UUID value wrapper. The description adds no additional parameter-level meaning, but none is needed since the schema fully documents roundId.

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 ('flips') and clearly identifies the resource and state transition: a CLOSED round becomes OPEN. The parenthetical '(status only)' further differentiates this from broader update operations, making the tool's purpose unambiguous.

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 implicitly establishes when to use the tool: when a closed cap table round needs to be reopened. It doesn't explicitly name alternatives like update_cap_table_round or close_cap_table_round, but the 'status only' clarification helps route the agent away from general-purpose updates.

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.