Lovie Company Formation

Get Cap Table Overview

cap_table_get_cap_table_overview

Read-only

Says which view of a company's cap table is the current one: the live roster, or the post-conversion table produced by the latest closed round. Read-only, and small — it returns the mode and that round's id, not the table. Use it first when you do not know whether a company has closed a priced round yet.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No
`latestRoundId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 10, 2026

addedOutput schema / properties / latestRoundId / anyOf

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

removedOutput schema / properties / latestRoundId / description
```
Removed value: -"UUID value wrapper."
```

removedOutput schema / properties / latestRoundId / properties

Removed value: -{
-  "value": {
-    "format": "uuid",
-    "type": "string"
-  }
-}

removedOutput schema / properties / latestRoundId / type
```
Removed value: -"object"
```

First observedAug 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already carry readOnlyHint true and destructiveHint false. The description adds useful behavioral context beyond annotations: it is 'small', returns only the mode and round id, and explicitly says it does not return the table. This clarifies the tool's lightweight nature and scope.

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 well-structured sentences with no filler: the first states the core behavior, the second adds scope and output details, the third gives a practical usage rule. Every sentence earns its place and key information is front-loaded.

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?

Given its single parameter, output schema, and read-only annotations, the description covers the essentials: what the tool returns, what it does not return, and when to use it. It could optionally explain the behavior when no round exists, but it is already sufficient for an agent to call it correctly.

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 input schema has 100% coverage for its single parameter (companyId), and the description does not discuss the parameter. The reference to 'a company's cap table' implicitly ties companyId to the target entity, but no additional semantic information is added beyond the schema. 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?

Description names a specific verb ('Says') and a precise resource: which view of a company's cap table is current. It explicitly distinguishes itself from table-content tools by noting it returns only the mode and round id, not the table. This makes it unmistakable against cap_table_get_cap_table_summary and cap_table_get_cap_table_round.

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 offers a clear condition for when to invoke this tool: 'Use it first when you do not know whether a company has closed a priced round yet.' This gives strong usage context, though it does not explicitly name sibling tools as alternatives or state exclusions, so it stops short of a 5.

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.