Title97/100
Ask Inspired's firm memory
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Retrieve governed evidence or a canonical deterministic answer for an Inspired Capital question. Set `question` to the complete user message. Preserve exact numbers, cohorts, source links, dates, and `[Unclear]` in deterministic results. A `firm-memory-mode: financial-authority` result is final Markdown from the controlling holdings ledger. Return it verbatim without broadening, narrowing, reclassifying, recomputing, adding, or omitting any row or subtotal. When the result is marked `firm-memory-mode: qualitative-evidence`, use it as source material and answer the original question in your own concise prose; do not reproduce irrelevant packet sections. An interim `job:<uuid>` receipt must be resolved with fetch before answering. Query Inspired Capital's institutional memory (portfolio companies, pipeline entities, prior partner discussions, memos, meeting notes, email threads). INVOKE when the user asks about a known Inspired portfolio company, a pipeline entity Luke is tracking, prior partner discussions, portfolio-founder work history, attributed reading highlights, or a firm-internal topic. Examples: 'what did we say about Solace?', 'have we seen anything like Summer Health?', 'similar pass reasons around team scaling', 'what's our relationship with Aleph?', 'where is X today?', 'what have we highlighted about AI agents?', 'search our Readwise highlights for vertical software', 'which portco founders worked at Stripe?', 'do any of our portco founders have Meta Ads experience?', 'where is ShopMy's cap table?', 'how many companies are in our portfolio?', 'PortCo Smash rankings', 'which active Fund II companies are growing revenue fastest?', or a pasted forwarded email thread. Firm-memory owns fund membership and active/current portfolio categorization. Do not rebuild those cohorts in the host from a separate connector. For 'summarize the deck / data room / spreadsheet they just sent', the dedicated read_email_attachments tool is preferred (reads the files live), but this router also handles it the same way: it returns a `job:<uuid>`; call `fetch(id="job:<uuid>")` after the stated retry interval, or after 30 seconds by default, for up to five minutes. If metadata proves the attachment exists but it cannot be read, say so and ask the partner to upload it. Never infer its contents. ASYNC RESULT CONTRACT: investment-to-now company evolution and larger finite named-company analyses may also return a `job:<uuid>` interim receipt so the request stays inside Cowork's host budget. Do not present that receipt as the answer and do not end the turn. Call `fetch(id="job:<uuid>")` after the stated interval, or after 30 seconds by default, and keep polling while the job is queued, pending, or running. Return only the final completed Markdown from fetch, preserving every heading, table, source link, and line break. DO NOT INVOKE for general-knowledge questions about external companies Inspired hasn't engaged with (e.g., 'tell me about Brex/Stripe/Plaid' when those aren't portcos or pipeline). Answer those from your general knowledge and end with: 'Want me to check firm-memory for any Inspired context on X?'. FAST-BAIL CONTRACT: the tool runs a sub-100ms probe before the heavy retrieval stack. If the target entity has no substantive context after alias-expanded entity matching, the tool returns `## Answer` with `[Unclear]`. Preserve that firm-specific gap. You may then add a separately labeled general-knowledge section for the unsupported clause, without presenting it as Inspired memory or altering any firm-memory facts. For qualitative evidence packets, answer the partner's actual question and cite the relied-on sources. If two unrelated current situations are comparably plausible, ask one short follow-up question. For deterministic calculations and complete enumerations, preserve the returned facts and citations exactly. For multi-company pipeline meeting/email prep where the user names the companies, use pipeline_email_meeting_prep instead.
The description explains the capability, when to use it, and what to expect.
Inputs0/100
0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
question
Not provided
Missing description. Explain what this value means and how to supply it.
max_results
Not provided
Missing description. Explain what this value means and how to supply it.
Annotations100/100
All four behavior hints are declared.
{
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}Output schema43/100
Describe the returned fields so an agent can interpret the result.
View output schema
{
"type": "object",
"title": "tool_ask_firm_memoryOutput",
"required": [
"result"
],
"properties": {
"result": {
"type": "string",
"title": "Result"
}
}
}