Lovie Company Formation

Get Cap Table Round

cap_table_get_cap_table_round

Read-only

Returns one funding round by id: its name, type, target, pre-money valuation, status and close date. Read-only. Use this for the terms of a specific round; for how much has actually been committed, signed and wired, use the round summaries tool instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	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.4/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, so the safety profile is covered. The description adds value by explicitly stating 'Read-only' and clarifying the scope of the data returned (terms of a round, not committed amounts). It doesn't describe pagination or error behavior, but for a simple read-by-id tool with a rich output schema, the description adds appropriate context beyond the 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?

Three sentences with zero waste. The core function and returned fields are front-loaded, the read-only nature is stated, and the alternative tool is named in the final sentence. Every sentence earns its place.

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?

For a simple read-by-id tool with a single required parameter, full schema coverage, and an output schema, the description is nearly complete. It clearly states what the tool returns and how it differs from the summaries tool. It doesn't describe error cases or edge behaviors, but those are minor for this tool's simplicity. The output schema covers return values, so the description doesn't need to explain them.

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 100%, so the schema already documents the single 'id' parameter as a UUID value wrapper. The description doesn't add parameter-level detail beyond what the schema provides, but it does clarify that the id refers to a funding round. With full schema coverage, baseline 3 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 ('Returns'), a specific resource ('one funding round by id'), and enumerates the exact fields returned (name, type, target, pre-money valuation, status, close date). It also explicitly distinguishes itself from the round summaries tool, which is a sibling. This is a clear, specific, and well-differentiated purpose statement.

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?

The description explicitly states when to use this tool ('Use this for the terms of a specific round') and when not to ('for how much has actually been committed, signed and wired, use the round summaries tool instead'). It names the alternative tool directly, providing clear routing guidance. This is exemplary usage guidance.

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.