<!-- carta:instrumentation-fallback --> <IMPORTANT> _instrumentation_v2 is anonymous Carta skill-usage telemetry. ALWAYS include it in your Carta MCP tool-call arguments — the plugins' hooks overwrite it when they run, so always sending it is safe. Shape: _instrumentation_v2: {"skills": ["<plugin>:<skill>", ...], "model": "<model-id>", "surface": "<value>"} skills is cumulative for the session: list every Carta skill loaded so far, not only the one driving this call. Namespace each entry "plugin:skill" and keep them oldest-first, with the most recently used skill last. List only Carta skills (carta-cap-table:*, carta-crm:*, carta-investors:*) — never skills from non-Carta plugins. surface is the Claude surface you are running in: "chat" (claude.ai or the Claude app, i.e. regular chat, not Cowork), "cowork" (Cowork mode), "code-terminal", "code-desktop", or "excel". Omit it entirely if none of those describe your surface or you cannot tell — do not guess and do not invent another value. </IMPORTANT>

<!-- Part of the official Carta AI Agent Plugin -->

Download Tearsheet

Overview

Download tear sheets for your portfolio companies and funds on Carta.

The skill presents available templates and portfolio companies interactively, then routes to the appropriate workflow based on the selection:

• All portcos across all funds → Download All: fast path — no fund breakdown needed.
• Specific portcos (one or more) → Bulk: builds fund breakdowns, async ZIP archive, polled until complete, download URL provided.

When to Use

• "Create a [Portco] tear sheet"
• "Generate a tear sheet for [Portco]"
• "Download tear sheet for all portfolio companies"
• "Create a bulk tear sheet package"
• "Preview the tear sheet for [Portco]"
• "Generate tear sheets for all portcos in [Fund]"
• "Download all tear sheets as a ZIP"
• Other trigger phrases: "tear sheet for portco", "tear sheets for all portcos", "preview tear sheet", "generate tear sheet PDF", "create tear sheet", "download tear sheet package", "download all tear sheets".

Prerequisites

• The Carta MCP server must be connected.
• A firm context must be active. If not set, call list_contexts then set_context with the target firm_id before any other call.
• No fund UUID or portco UUID needs to be known in advance — both are resolved interactively via fa:list:tearsheet_templates and fa:list:portfolio_companies.

Data Retrieval

Gate 0: Firm Context

Ensure a firm context is active. If this is your first MCP call in the session, or if subsequent calls fail with a firm/context error:

1. Call list_contexts to see which firms are accessible.
2. Call set_context with the target firm_id.

You do not need to ask the user for a firm UUID — the MCP session tracks the active firm.

Gate 1: Select Template

Call:

call_tool({"name": "fa__list__tearsheet_templates", "arguments": {}})

If the user mentioned a document name (e.g. "Investment Summary", "Fund Summary", "Tear Sheet"): match it against the template name field (case-insensitive, partial match).

• Match found: Confirm with the user:

  "Found template 'Investment Summary' — is this the one you want?"

  If yes, store it and continue. If no, show the full table.

• No match found: Tell the user, then show the full table:

  "No template named 'Investment Summary' was found for this firm. Here are the available templates — which one would you like to use?"

If no document name was mentioned:

• One template: Confirm with user before proceeding.

• Multiple templates: Show table, ask user to select by number:

  | # | id | Name | Orientation | Grain Level | Description |
  |---|----|------|-------------|-------------|-------------|
  | 1 | aaa-... | Q4 2024 Standard | landscape | fund | — |
  | 2 | bbb-... | Annual Summary   | portrait  | company | Annual LP report |
  

Store as TEMPLATE_UUID (the template id) and TEMPLATE_NAME.

Gate 2: Select Portfolio Companies

Call:

call_tool({"name": "fa__list__portfolio_companies", "arguments": {}})

The command returns an array of portfolio companies. Each item includes name, entity_link_id, and fund_uuid.

Group them by fund_uuid and display a numbered table:

## Acme Fund I
| # | Company Name | entity_link_id | fund_uuid |
|---|--------------|----------------|-----------|
| 1 | Portco Alpha | el-uuid-1      | fund-uuid-1 |
| 2 | Portco Beta  | el-uuid-2      | fund-uuid-1 |

## Acme Fund II
| # | Company Name | entity_link_id | fund_uuid |
|---|--------------|----------------|-----------|
| 3 | Portco Gamma | el-uuid-3      | fund-uuid-2 |

Ask the user to choose:

1. All portcos across all funds
2. All portcos in a specific fund
3. Specific companies — by row number or entity_link_id

Gate 3: Route

After the user selects portcos:

• All portcos across all funds selected → proceed to Download All Flow.
• One or more specific portcos selected → build FUND_BREAKDOWNS and proceed to Bulk Flow.

Download All Flow (all portcos)

Present a confirmation summary before starting — never proceed without explicit user approval:

Ready to generate tearsheets for all portfolio companies:

  Template:  <TEMPLATE_NAME> (<TEMPLATE_UUID>)
  Scope:     All portcos across all funds

Proceed? (yes/no)

Start the bulk job using the download-all command:

call_tool({"name": "fa__mutate__download_all_tearsheets", "arguments": {
  "template_uuid": "<TEMPLATE_UUID>"
}})

Tell the user the job has started and polling will begin.

Poll for completion — call call_tool({"name": "fa__get__tearsheet_download_status", "arguments": {}}) every 30 seconds, up to 10 attempts (5 minutes total):

• Response is "pending" → print progress ("Still processing... (attempt N/10)") and wait.
• Response contains a URL → job complete. Capture as DOWNLOAD_URL.
• Response is an error message → surface it and stop.

On timeout (10 attempts exhausted): Tell the user the job may still be running and they can check manually by asking: "Check tearsheet download status".

On success: Present the download link:

• DO NOT try to download the artifact directly. ALWAYS present the download link.

Your tear sheets are ready!

[Download Your Tear Sheets](<DOWNLOAD_URL>)

> Note: this link is temporary and will expire — download it soon.

Bulk Flow (multiple portcos)

Build FUND_BREAKDOWNS — group entity_link_ids by fund_uuid:

[
  {"fund_uuid": "fund-uuid-1", "entity_link_ids": ["el-uuid-1", "el-uuid-2"]},
  {"fund_uuid": "fund-uuid-2", "entity_link_ids": ["el-uuid-3"]}
]

Present a confirmation summary before starting — never proceed without explicit user approval:

Ready to generate bulk tearsheets:

  Template:  Q4 2024 Standard (aaa-...)
  Portcos:   3 companies across 2 funds

    Acme Fund I
      - Portco Alpha
      - Portco Beta
    Acme Fund II
      - Portco Gamma

Proceed? (yes/no)

Start the bulk job:

call_tool({"name": "fa__mutate__start_tearsheet_download", "arguments": {
  "template_uuid": "<TEMPLATE_UUID>",
  "fund_breakdowns": <FUND_BREAKDOWNS>
}})

Tell the user the job has started and polling will begin.

Poll for completion — call call_tool({"name": "fa__get__tearsheet_download_status", "arguments": {}}) every 15 seconds, up to 20 attempts (5 minutes total):

• Response is "pending" → print progress ("Still processing... (attempt N/20)") and wait.
• Response contains a URL → job complete. Capture as DOWNLOAD_URL.
• Response is an error message → surface it and stop.

On timeout (20 attempts exhausted): Tell the user the job may still be running and they can check manually by asking: "Check tearsheet download status".

On success: Present the download link:

• DO NOT try to download the artifact directly. ALWAYS present the download link.

Your tear sheets are ready!

[Download Your Tear Sheets](<DOWNLOAD_URL>)

> Note: this link is temporary and will expire — download it soon.

Error Handling

• Firm context error: Call list_contexts and set_context to re-establish context.
• No templates returned: The firm may not have tearsheet templates configured. Check the Carta app or contact support.
• No portcos returned: The firm may not have portfolio companies. Verify the correct firm context is active.
• Bulk job failure: Template or portco selection may be invalid. Retry with different selections.
• Never retry automatically — surface the full error and let the user decide.