Lovie Company Formation

Get Cap Table Summary

cap_table_get_cap_table_summary

Read-only

GetCapTableSummary returns company-wide AGGREGATES on the fully-diluted roster: total shares, stakeholder count, founders' combined percentage, and ownership split by stakeholder type. Read-only. Aggregate only. "Per-type segments" groups by type (founder, investor, employee) and is not a per-holder breakdown — it cannot tell you what any one person holds. Use GetListCapTableSecurities for that.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`segments`	No
`foundersPct`	No
`totalShares`	No
`asOfRecordedAt`	No
`totalCommitted`	No
`totalInvestment`	No
`authorizedShares`	No
`stakeholderCount`	No
`authorizedCommonShares`	No
`authorizedPreferredShares`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 10, 2026
- addedOutput schema / properties / asOfRecordedAt / anyOf
```
Added value: +[
+  {
+    "format": "date-time",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / asOfRecordedAt / format
```
Removed value: -"date-time"
```
- removedOutput schema / properties / asOfRecordedAt / 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 and destructiveHint=false, so 'Read-only' largely repeats structured data. However, the description adds real behavioral context beyond the schema by clarifying that 'Per-type segments' is a group-by-type rollup, not a per-holder view. That semantic constraint is valuable and not encoded anywhere else.

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 and the key limitation, and every sentence carries weight. Minor redundancy between the all-caps 'AGGREGATES' and the later 'Aggregate only' phrase, but overall efficient.

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?

An output schema exists, so return values need not be explained. For a read-only aggregate tool, the description covers purpose, scope, and the sibling alternative completely; nothing an agent needs to call it correctly is missing.

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 50% (companyId is documented as a 'UUID value wrapper', asOf has no description), yet the description says nothing about either parameter. It does not compensate for the coverage gap by explaining what asOf does or the as-of-date semantics.

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 (GetCapTableSummary) and enumerates exactly what it returns: total shares, stakeholder count, founders' percentage, and ownership split by type. It explicitly distinguishes itself from a per-holder breakdown, so an agent can tell it apart from sibling cap-table tools without opening the schema.

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 bounds when NOT to use it ('Aggregate only... not a per-holder breakdown — it cannot tell you what any one person holds') and routes to the correct alternative, GetListCapTableSecurities. This is exactly the when/when-not/alternative guidance an agent needs.

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.