Update to Maven Bio

{
  "description": "Return the round-by-round financing record (amounts, dates, investors, provenance) for a named company, or filtered by indication, mechanism, target, or investor. Use when someone wants the actual rounds, for example 'list the funding rounds for X', 'who invested in their Series B'. Use funding-landscape when they want a market-level capital picture rather than a round list.",
  "included_files": [
    {
      "relative_path": "LICENSE",
      "size_in_bytes": 802
    },
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 327
    }
  ],
  "name": "trace-financings",
  "skill_md_contents": "---\nname: trace-financings\ndescription: \"Return the round-by-round financing record (amounts, dates, investors, provenance) for a named company, or filtered by indication, mechanism, target, or investor. Use when someone wants the actual rounds, for example 'list the funding rounds for X', 'who invested in their Series B'. Use funding-landscape when they want a market-level capital picture rather than a round list.\"\n---\n\n# Trace Financings\n\n## Using this skill\n\nUse the connected Maven Bio MCP server at `https://mcp.mavenbio.com/`. Follow the user's explicit scope, depth, and output preferences; the workflow and output structure below are defaults. Report coverage limits instead of silently narrowing an explicitly requested set.\n\nHyphenated primitive names refer to other skills in this Maven Bio bundle. Consult the relevant skill when composing its workflow. Use the available MCP tool schemas for arguments; pass document identifiers to `read_document` through `ids`, and include a claim-specific `query` when using `format=\"citations\"`.\n\nThis primitive turns a funding question into a structured round set with explicit value disclosure status, investor mix, and document provenance.\n\n## Use When\n\n- the question is fundamentally about funding rounds, not drug programs or trials\n- a workflow needs capital activity for a company, an indication, a mechanism, a target, or an investor\n- you need round-level evidence (date, type, value, recipient, investors, supporting documents) before reasoning about runway, momentum, or investor signal\n\n## Core Tools\n\n- `get_financings` for structured cross-company filters (recipient, investor, financing_type, value range, date window, current-only, sort by total_value)\n- `search_entities(\"financing\", ...)` for natural-language financing discovery and fuzzy phrasings the structured params cannot express\n- `research_entity(name, \"company\", aspects=[\"financings\"])` for rounds where a named company was the recipient\n- `research_entity(name, \"company\", aspects=[\"investments\"])` for rounds where a named company was an investor (VCs, corporate venture arms, strategic investors)\n- `get_financings` with a recent date window (newest first) for the recency feed of newly announced rounds -- financing recency is not in `get_recent_events`\n- `read_document` against the round's `document_ids` to back any material claim\n\n## Tool Choice\n\n- if the agent already knows the named company, use `research_entity` aspects -- one credit, one shape, no resolution overhead\n- if the question is structured (\"Series B+ rounds in NSCLC since 2024\", \"rounds led by ARCH or Founders Fund\", \"rounds over $100M\"), use `get_financings` with typed filters\n- if the question is fuzzy or compositional (\"late-stage immuno-oncology momentum\", \"biotech IPOs this year\"), use `search_entities(\"financing\", ...)` and let the natural-language path translate it\n- for \"what's new this week\" feed-style questions, use `get_financings` with a recent date window; financing recency lives in `get_financings`, not `get_recent_events` (which covers only fda/trial/press)\n\n## Output Contract\n\nReturn a structured round list with:\n\n- `round_id` (the prefixed `fin_` identifier)\n- `financing_date`\n- `financing_type` (canonical: Pre-Seed, Seed, Series A, Series B, Series C, Series D+, IPO, Post-IPO Equity, Debt Financing, Grant, Strategic Investment, Acquisition, Other Financing)\n- recipient companies as `{id, name}` pairs\n- investor companies as `{id, name}` pairs\n- `total_value_usd` and `value_status` (`\"confirmed\"` or `\"unconfirmed\"`)\n- supporting `document_ids` for chaining into `read_document`\n- evidence rating per material claim\n- explicit gaps for unconfirmed rounds, missing investors, or contradictory sources\n\n## Aggregation Shortcut\n\nIf the question is \"totals, distributions, or rankings across a financing slice,\" prefer `aggregate_records(entity_type=\"financing\", ...)` and use `get_financings` to fetch round-level evidence for the claims you cite. `median`/`avg` aggregations on `total_value` already separate the confirmed-value denominator via `_input_count`.\n\n## Quality Bar\n\n- never present `total_value_usd: null` as \"the round was undisclosed\" -- the correct phrasing is \"Maven's data does not have the value.\" The round may have a publicly disclosed amount Maven has not captured. Verify externally if the value is critical.\n- when reporting aggregate totals (sum raised, average round size), separate the confirmed-value slice from the unconfirmed slice rather than treating null as zero\n- treat the canonical financing types as a closed enum; if a caller-supplied type alias resolves to a canonical value, surface the resolution explicitly so downstream readers see the normalization\n- for round-level claims (lead investor, oversubscription, valuation, post-money), require document evidence from `read_document`; the structured row alone is metadata, not citable evidence\n- the investor list may include thin-profile stub companies for previously-unknown investors -- these resolve via `research_entity` but with limited data; preserve the asymmetry rather than smoothing it over\n- distinguish `get_financings` (private/round-level capital activity) from `get_financials` (public-market financial statements: revenue, EBITDA, market cap, cash). Both can apply to the same company; do not conflate them\n- when sorting by deal size, use `sort_by=\"total_value\"` and note that unconfirmed rounds are ordered last\n\n## Fallback Rules\n\n- if a recipient or investor name does not resolve, the response surfaces ranked candidates under `error.alternatives` keyed per input. Retry with a candidate name in one round-trip rather than guessing\n- if a `financing_type` value does not match the canonical enum, the response either auto-corrects (case-fold or alias) and surfaces the correction, or rejects with the canonical list under `error.alternatives`. Use the canonical list, do not invent new types\n- if `get_financings` returns zero rows for a structured query, retry with `search_entities(\"financing\", \"<the same intent in natural language>\")` before concluding no rounds exist\n- for indication / mechanism / target ontology axes, the recipient-side filters live on `search_entities(\"financing\", ...)`; the structured `get_financings` surface does not expose them as typed params\n- if host web fetch is blocked, prefer `search_documents` plus `read_document` against the round's `document_ids` rather than retrying blocked external fetches\n- if a financing question remains blocked after the above, state the gap explicitly in the output rather than substituting a weaker proxy answer\n"
}