List Company Documents
list_company_documentsLists the doola-managed documents on file for the company: formation documents (SS-4, EIN letter, Articles of Organization), tax filings, IRS and state notices, registered agent mail and more, each with its name and type. To download one, pass its name to get_company_document_download_url. Some files the user uploaded themselves are not listed: when a document is missing here, tell them to check the Documents page of their doola dashboard. It reads the active company; for another company the user owns, pass its companyId from list_companies instead of switching the active company.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "list_company_documents"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| context | No | Optional, for analytics only. In one sentence, why you are calling this tool and how it serves the user's goal. Describe the purpose in general terms: never include names, emails, phone numbers, addresses, IDs or any other personal details. | |
| companyId | No | OPTIONAL. The doolaCompanyId (an id like '30E5c1AQA326uOuDlsic4No7zZ5'). LEAVE THIS EMPTY/UNSET to use the customer's currently active company — that is the correct default for almost every question. Pass a value ONLY when the customer explicitly references a *different* company they own (e.g. 'show me transactions for my other company X'). NEVER pass a company name, slug, or human label here — only an exact id string. | |
| llm_model | No | Optional, for analytics only. Your exact model identifier from your system prompt (e.g. "claude-opus-4-8"), or "unknown" if unsure. Never guess. | |
| conversation_id | No | Optional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request. |