Lovie Company Formation

Generate Cap Table Summary PDF

cap_table_generate_cap_table_summary_pdf

GenerateCapTableSummaryPdf renders the cap-table summary to a branded PDF on the backend document engine (Gotenberg). It returns the bytes, or with as_link (always, for an assistant) a short-lived download link to give the user. Read-only.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`pdf`	No
`downloadUrl`	No
`downloadUrlExpiresAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 8, 2026

addedInput schema / properties / asLink
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / downloadUrl
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / downloadUrlExpiresAt

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

First observedAug 11, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Adds real context beyond the annotations: it discloses the backend engine (Gotenberg), that output is either bytes or a short-lived download link, and that the operation is read-only. Annotations only cover openWorldHint=false and destructiveHint=false, so this enriches the behavioral picture meaningfully.

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?

Three compact sentences with the purpose front-loaded and no wasted filler. Minor redundancy in restating the PascalCase identifier 'GenerateCapTableSummaryPdf' in the opening clause rather than describing the action directly.

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?

An output schema exists, so return values need not be spelled out, yet the description usefully notes the bytes-vs-link dichotomy. Annotations cover the safety profile. It is complete enough to invoke correctly, with only the absence of alternative-routing guidance as a gap.

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 coverage is 50%: companyId carries only a generic 'UUID value wrapper' note while asLink has no schema description. The description partially compensates by explaining asLink's effect (short-lived download link) and when to set it, but adds nothing for companyId. Baseline 3 is appropriate given the partial coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: it 'renders the cap-table summary to a branded PDF.' The resource (summary PDF) is distinct from sibling generators like generate_cap_table_agreement_pdf and generate_cap_table_docs. It does not explicitly name those siblings, so it stops short of a 5.

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

Usage Guidelines2/5

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

No when-to-use versus alternatives guidance relative to siblings such as get_cap_table_summary or get_cap_table_agreement_pdf_url. The only directive is the parenthetical '(always, for an assistant)' on as_link, which is parameter instruction rather than tool-selection guidance. Context is implied at best.

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.