Skip to main content
Glama

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 with the backend document engine (Typst). It returns the bytes, or with as_link (always, for an assistant) a short-lived download link to give the user. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "companyId": "<companyId>"
    },
    "name": "cap_table_generate_cap_table_summary_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
asLinkNo
companyIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
pdfNo
downloadUrlNo
downloadUrlExpiresAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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"
      +    }
      +  ]
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare openWorldHint=false and destructiveHint=false; the description adds that the tool is read-only, uses Typst, returns bytes by default, and can produce a short-lived download link. It does not discuss permissions or link-expiry details, but it adds meaningful behavior 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three short sentences, front-loaded with the action and output form. The repeated CamelCase tool name and trailing 'Read-only' are slightly redundant, but the wording is efficient overall.

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 two-parameter read-only generation tool with an output schema, the definition covers the output form and the optional link mode. Missing detail on companyId and permissions is minor given the tool's simplicity and the presence of an output schema.

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 50%. The description explains asLink's purpose as a short-lived download link especially for an assistant, but it does not explain the required companyId UUID wrapper. It adds useful meaning for one parameter while leaving the other to the schema.

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?

The description gives a specific verb ('renders') and resource ('cap-table summary') and names the output format (branded PDF), so the tool's action is clear. It does not explicitly contrast with sibling summary or PDF tools, but the resource is distinct enough to identify it.

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

Usage Guidelines3/5

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

It implies use when the user needs a downloadable cap-table summary PDF and explains that as_link is effectively always appropriate for an assistant giving the user a link. However, it does not state when to prefer this over cap_table_get_cap_table_summary or other PDF-generation siblings, nor does it list preconditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.