commitment-history
ChatGPTCalculate aggregate net performance values (NAV, Called, Distributed, Unfunded, Net IRR, Net MOIC, Commitment Amount) across commitment history. Use this tool when: - The user requests net fund performance metrics (e.g., "what is the net IRR for Fund X?") - The user requests commitment-level values (e.g., "what is my NAV?", "how much has been called?") - The user asks about portfolio performance without specifying gross (net is the default) CRITICAL: - These are net performance values. For gross performance values (Gross IRR, Gross MOIC, cost, realized, unrealized), use the fund-returns tool instead. - If you are unsure whether the user is asking for gross or net performance, you MUST get explicit confirmation before proceeding. - Do NOT assume a currency. When querying specific funds, use the run-query tool to query funds with reporting_currency: true filtered by fund ID to determine the fund's reporting currency, then use that currency. Only ask the user if the reporting currency cannot be determined. Context: Users MUST trust the values provided; therefore, it's imperative that you reference the response's context object to contextualize results when presenting them: - context.currency: The currency of the returned values; always include unless the user explicitly specified a currency in their request - context.date: The as-of date for the returned metrics; always include unless the user explicitly specified a date in their request - context.type: Always "net" — distinguish this from gross performance when presenting to the user
entity-search
ChatGPTRetrieve companies, funds, groups, and general partners via substring similarity search. Use run-query to filter by specific properties like industry or sector (GICS naming, e.g. "Health Care", not "Healthcare"). Do not include "group" in the query when searching for groups.
fund-returns
ChatGPTQuery gross fund-level performance data (cost, realized, unrealized, gross MOIC, gross IRR). Use this tool when: - The user requests gross fund performance metrics (e.g., "what is the gross MOIC for Fund X?") - The user requests fund-level cost, realized, and unrealized values (e.g., "what is the total cost for Fund X?") - The user asks about a fund's investment performance or returns (e.g., "how is Fund X performing?", "what are the returns for Fund X?") CRITICAL: - These are gross performance values. For net performance values (Net IRR, Net MOIC, DPI, RVPI, NAV, Called, Distributed), use the commitment-history tool instead. - If you are unsure whether the user is asking for gross or net performance, you MUST get explicit confirmation before proceeding. - Unless the user asks for historical or multi-period data, you MUST pass the date argument. Context: Users MUST trust the values provided; therefore, it's imperative that you reference the response's context object to contextualize results when presenting them: - context.currency: The currency of the returned values; always include unless the user explicitly specified a currency in their request - context.date: The as-of date for the returned aggregate metrics or null for time series; always include unless the user explicitly specified a date in their request - context.type: Always "gross" — distinguish this from net performance when presenting to the user Source Citations: - Each fund return record may include a document_tags object, grouped by field name (e.g. { cost: [...], realized: [...] }). Each annotation provides filename, page, and document_id identifying the source document the value was extracted from. - When presenting values to the user, cite the source filename and page number alongside the relevant value so the user can verify the data against its source. If multiple values share the same source document and page, a single citation after the group is sufficient.
get-help-center-article
ChatGPTRetrieve the complete content of a specific Chronograph help center article using its article ID. This tool fetches the full text content of documentation articles, typically used after finding relevant articles with the "query-help-center-documentation" tool. The article ID can be obtained from the search results of help center queries.
investment-metrics
ChatGPTCalculate a single metric across investments. Useful for aggregating and tracking performance metrics. Call this tool with `query: {help: true}` first to enumerate options and required params before attempting to query. REQUIRED WORKFLOW — never skip step 1: 1. ALWAYS call with query: {help: true} first. The help response contains usage_hints that are the authoritative guide for how to interpret the user's request and which fields to use. If the user's intent is ambiguous after reading usage_hints, ask the user to clarify before querying. 2. Only then call with a metric query using the guidance from step 1. CRITICAL — choosing metric.type vs metric.metricDefinitionId (decide BEFORE calling this tool): - The hardcoded performance types are: gross_irr, gross_moic, cost, realized, unrealized (plus LP-only calculated_gross_irr, reported_gross_irr, remaining_cost, ownership). - If the user asks for one of the hardcoded performance types above, set metric.type to that value. - For ANY other metric the user mentions by name — Revenue, EBITDA, headcount, named KPIs, custom or user-defined metrics, anything that sounds like a company financial — you MUST call the metric-definition-search tool first. It performs fuzzy matching (e.g., "Revenu" => "Revenue") and returns the canonical metric definition with a numeric id. Pass that id to this tool as metric.metricDefinitionId. Do this even if the metric appears in help mode's metric_type_options. - Do NOT guess or infer metric.type values. Do NOT call this tool with a speculative metric.type and rely on errors to redirect you. - Exactly one of metric.type or metric.metricDefinitionId must be provided. Date Resolution: - If the user asks for "latest available data", "most recent", or "most recent reporting date", set date = "last" (when the metric accepts "last" as a valid date input). - If the user asks for "earliest" data, set date = "initial" (when the metric accepts "initial" as a valid date input). Context: Users MUST trust the values provided; therefore, it's imperative that you reference the response metadata to contextualize results when presenting them: - currency: The currency of the returned values; always include unless the user explicitly specified a currency in their request - metricParams.date: The as-of date for the returned metrics; always include unless the user explicitly specified a date in their request - metricParams.period: The period used (e.g., LTM, Quarter); always include when applicable - metricParams.scenario: The scenario used (e.g., Actual); include when not the default - metricParams.applySplit: When present, true means the value is the LP's share (commitment-scaled); false means the fund-level total. Always include this in responses to the user when applySplit was relevant. - metricParams.navScaling: When present (only on unrealized), true means LP-share was NAV-scaled; false means commitment-scaled. Include when explaining unrealized results. - investmentsCount: The number of investments contributing to the result (after null-value filtering); omitted for grouped aggregations — use result.groupedAggregates[].investmentCount instead - When date is "current", "initial", or "last", the as-of date varies per investment ("current" resolves to each fund's current reporting date; "initial"/"last" resolve based on data availability). result.investments[].metric_date shows the actual resolved date for each investment.
metric-definition-search
ChatGPTSearch for metric definitions by name using fuzzy matching. Returns matches to help find the correct metric even with typos or variations (e.g., "Revenu" => "Revenue"). Use this when the user mentions a metric by name or you need a metric definition ID. Results include id, labeled_as (display name), description, base_metric_entity (can be: 'Company', 'Investment', or null), format_as, and is_balance. When is_balance is true, use period 'As of' for point-in-time; when false, use trailing periods (e.g. LTM, Quarter).
query-help-center-documentation
ChatGPTSearch and discover relevant help documentation articles for the Chronograph platform. This tool queries the help center knowledge base to find articles that match your search term and returns a list of relevant articles with their metadata (id, name, preview, etc.). Use this tool for questions about how Chronograph features work, platform capabilities, user guides, and troubleshooting. This tool should also serve as a fallback when other specialized Chronograph MCP tools cannot directly address a user's request. Note: This tool returns article previews and metadata only - use the "get-help-center-article" tool with the returned article id to retrieve the full content of any specific article.
run-query
ChatGPTList/retrieve core entities and their details, or enumerate filter options and entity IDs for use in other tools
semantic-search
ChatGPTSearch reporting and financial documents for specific information such as business updates, key initiatives, financial performance, or investment activity. Returns relevant document pages matching the query. Do not use this as a general search — use entity-search to look up companies, funds, or other entities.
top-exposures
ChatGPTList your top LP-level company exposures by invested, realized, or unrealized amount, along with company details. Returned cost, realized, unrealized, and remaining_cost values are the LP's share (commitment-scaled by default; pass navScaling: true to use NAV scaling on unrealized).
