Skip to main content
Glama

Get Company Document Download Link

get_company_document_download_url
Read-only

Returns a download link for one document from list_company_documents, such as the Articles of Organization or the EIN letter. Pass the document's name exactly as listed. Give the user the link as a download link named after the document, exactly as returned, and never open or fetch it yourself: it works for up to an hour after this call, so call again for a new one instead of reusing an old link. The result never holds the document's contents. When there is no link, share documentsPageLink, where the user opens the file in their doola dashboard. Answer in plain language and never show the user the field names. 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

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": {
      "documentName": "<documentName>"
    },
    "name": "get_company_document_download_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNoOptional, 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.
companyIdNoOPTIONAL. 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_modelNoOptional, for analytics only. Your exact model identifier from your system prompt (e.g. "claude-opus-4-8"), or "unknown" if unsure. Never guess.
documentNameYesthe exact `name` of the document as list_company_documents returns it; call list_company_documents first when it is not known
conversation_idNoOptional, 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/destructive hints, it discloses the key behaviors an agent could get wrong: the link expires in about an hour, the result never contains document contents, and the agent must not fetch or open the URL itself but hand it to the user named after the document. The documentsPageLink fallback adds further operational context.

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 core constraint (what the link is, that it expires, that it must not be fetched) is front-loaded and the alternative path follows. It runs long and mixes in presentation rules about field names and plain language that are peripheral to invoking the tool, costing some tightness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so: it states the result is a link only, not document contents, and defines a fallback field for the no-link case. Combined with the expiry and company-scoping notes, an agent has everything needed to call and act on it correctly.

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 100%, so every parameter including the analytics fields is already documented in structured data; the description mostly restates the documentName and companyId contract. Its one added nuance is confirming the name must match what list_company_documents returns, which is already present in the schema, so baseline 3 applies.

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?

It names a specific verb and resource ('Returns a download link for one document') and anchors it to a sibling source ('from list_company_documents, such as the Articles of Organization or the EIN letter'), so the agent immediately knows what artifact this produces and where the input comes from.

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

Usage Guidelines5/5

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

Explicit when-to-use and how-to-use rules are given: pull the name from list_company_documents first, pass it exactly, pass companyId from list_companies rather than switching the active company, and re-call for a fresh link instead of reusing an expired one. It also names the fallback (documentsPageLink) when no link exists.

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.