Lovie Company Formation

Generate Cap Table Agreement PDF

cap_table_generate_cap_table_agreement_pdf

Destructive

Renders the PDF for one employee equity-grant agreement (option/rsu/rsa/fast) and stores it; returns the S3 key. Generation is idempotent: when the agreement already has a PDF this returns it unchanged. A signed or void agreement is refused. regenerate=true (overwrite the existing PDF in place) is refused for assistants — ask the person to press Regenerate PDF in the app — and for any agreement out for signature.

Input Schema

TableJSON Schema

Name	Required	Description
`companyId`	Yes	UUID value wrapper.
`regenerate`	No
`agreementId`	Yes	UUID value wrapper.
`templateFields`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`s3Key`	No
`regenerated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 1, 2026
- addedInput schema / properties / regenerate
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / regenerated
```
Added value: +{
+  "type": "boolean"
+}
```

Changed1 schema field changedSep 10, 2026

addedInput schema / properties / templateFields

Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "type": "object"
+}

First observedAug 11, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only provide destructiveHint=true and openWorldHint=false; description adds substantive traits: PDF storage, S3 key return, idempotency, refusal cases, and assistant restriction on regenerate. This exceeds annotation coverage and aligns with 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?

Four tight sentences, front-loaded with core action and return, then conditions. No filler.

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 an output schema exists, return values need not be detailed; annotations cover safety and description covers idempotency/refusals. Still incomplete on templateFields semantics, but otherwise complete for correct invocation.

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%; description explains regenerate=true overwriting behavior and ties agreement types, but does not explain templateFields or add meaning for required UUID wrappers companyId/agreementId. It partially compensates for the coverage gap.

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?

Specific verb 'Renders the PDF' and resource 'one employee equity-grant agreement (option/rsu/rsa/fast)' plus storage/return. Distinguishable from sibling bulk/summary generation tools by its single-agreement scope.

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?

States idempotent behavior, refuses signed/void agreements, and gives explicit constraints for regenerate with an alternative (press Regenerate PDF in app). Lacks broader when-to-use guidance versus sibling generation endpoints (e.g., generate_cap_table_docs).

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.