Back to tracker
Plugin tracker
Tools
Explore what tracked Claude Connectors and ChatGPT Plugins can actually do. Search by tool, Plugin, Brand, category, verb, or access requirement.
Latest snapshot2026-09-11USmethodology registry-public-v1
Searchable tools
113,017
Authless tools
7,424
Auth required
100,766
Described tools
61,166
113,017 tools
- get_destination_setup_infogetWindsor.ai for Paid MediaWindsor
ConnectorrequiredData & Analytics - get_destination_tasksgetWindsor.ai for Paid MediaWindsorConnectorrequiredData & Analytics
- get_destinationsgetWindsor.ai for Paid MediaWindsorConnectorrequiredData & Analytics
- get_fieldsgetWindsor.ai for Paid MediaWindsorConnectorrequiredData & Analytics
- get_optionsgetWindsor.ai for Paid MediaWindsorConnectorrequiredData & Analytics
- get_subscription_urlgetWindsor.ai for Paid MediaWindsorConnectorrequiredData & Analytics
- get_windsor_login_urlgetWindsor.ai for Paid MediaWindsorConnectorrequiredData & Analytics
- list_actionslistWindsor.ai for Paid MediaWindsorConnectorrequiredData & Analytics
- create-uploadcreateorigami.publica.laPublica.laConnectorrequiredCommerce
- finalize-publicationfinalizeorigami.publica.laPublica.laConnectorrequiredCommerce
- get-accountgetorigami.publica.laPublica.laConnectorrequiredCommerce
- get-account-usagegetorigami.publica.laPublica.laConnectorrequiredCommerce
- get-download-linkgetorigami.publica.laPublica.laConnectorrequiredCommerce
- get-publicationgetorigami.publica.laPublica.laConnectorrequiredCommerce
- get-publication-readergetorigami.publica.laPublica.laConnectorrequiredCommerce
- get-run-reportgetorigami.publica.laPublica.laConnectorrequiredCommerce
- get-tool-rungetorigami.publica.laPublica.laConnectorrequiredCommerce
- list-publication-fileslistorigami.publica.laPublica.laConnectorrequiredCommerce
- list-publicationslistorigami.publica.laPublica.laConnectorrequiredCommerce
- list-tool-runslistorigami.publica.laPublica.laConnectorrequiredCommerce
- list-toolslistorigami.publica.laPublica.laConnectorrequiredCommerce
- run-toolrunorigami.publica.laPublica.laConnectorrequiredCommerce
- sync-publication-readersyncorigami.publica.laPublica.laConnectorrequiredCommerce
- Fetch MSCI Index & Related Datafetch · Fetch point-in-time MSCI Index, Constituent, Security, AUM, Dividend, and Corporate Event data for one calc_date. Same input shape and snapping rules as the v1/v2 variant (datapoints + codes + date in YYYYMMDD, optional currency/variant/page/page_size/order_by/order_direction/info_points), with one response shape change: list-cardinality datapoints come back as pandas-friendly tables. TOOL CHOICE: only call this with datapoints whose `supports_single_day=true` (in search_index_datapoints results). For datapoints with `supports_range=true` and a question about history / a date range, call `fetch_index_timeseries` instead. When you request multiple list datapoints from the same parallel response, the sort propagates alignment via the shared key (msci_security_code), so page 1 returns top weights paired with their actual ISINs. Returns `{ requested_date, fetched_date, note?, scalars, list_tables? }`. `scalars` is `{"{index_name} ({code})": { datapoint_id: value }}` — same nested shape as v2 fetch_data. `list_tables` carries one entry per (entity × list datapoint), each with a `{ columns, rows }` table where the first column is `date` (the same fetched_date value repeated). Pandas: `pd.DataFrame(t["rows"], columns=t["columns"])` — identical ingest to the v3 timeseries `list_tables` so callers can concatenate single-date and range results into one DataFrame. Each list entry also exposes a `pagination` block (`page`, `page_size`, `total_rows`, `total_pages`) for clients that need to page through large universes. Errors per-datapoint surface inside `scalars[entity][datapoint_id]` as `{ error, hint }` objects: `SINGLE_DATE_NOT_SUPPORTED`, `STRICT_GATE_VIOLATION`, etc. Do NOT call this in a loop to build a timeseries — use fetch_index_timeseries.MSCI ConnectorMSCI
PluginrequiredData & Analytics - Fetch MSCI Index & Related Time Seriesfetch · Fetch a history of MSCI Index, Constituent, Security, AUM, Dividend, and Corporate Event datapoint values over a date range. Use this whenever the user asks for a series, a chart, a return over a period, or "from X to Y". TOOL CHOICE: only call this with datapoints whose `supports_range=true` (in search_index_datapoints results). For point-in-time questions against datapoints with `supports_single_day=true`, call `fetch_index_data`. Inputs: `datapoints` = IDs from search_index_datapoints where `supports_range` is true; `codes` = entity codes matching each datapoint's entity_type; `start_date` / `end_date` = YYYYMMDD. Optional: `frequency` (daily | monthly — month-end-only datapoints are forced to monthly), `currency`, `variant`. You may pass multiple datapoints from the SAME dataset in one call (e.g. `equity_index.constituents.closing_weight` AND `equity_index.constituents.identifiers.isin`) — they coalesce into a single V1 request and arrive aligned in the same list table. Returns `{ errors, table, list_tables? }`. `table` is a pandas-friendly JSON table for scalar datapoints: `{ columns, rows }` where `columns[0] = "date"` (YYYYMMDD) and each subsequent column is `"{index_name} ({code}) {datapoint_id}"`; missing cells are `null`. Pandas: `pd.DataFrame(t["rows"], columns=t["columns"])`. List-cardinality datapoints (constituents, per-security identifiers, weights, etc.) come back in `list_tables[]` instead — one entry per (entity × datapoint), each carrying its own long-format `{ columns, rows }` with `date` as the first column. Same pandas idiom applies. Use `page` / `page_size` to control per-date pagination, and `order_by` / `order_direction` to drive sort order — sorting propagates row alignment across parallel datasets within each date so top weights stay paired with their actual ISINs at every date in the range. `errors[]` reports per-datapoint issues: `RANGE_NOT_SUPPORTED` (use fetch_index_data for that one), `STRICT_GATE_VIOLATION` (variant/currency mismatch — see the datapoint's `strict_gate` block in search results; switch to the suggested `fallback_id`), `RANGE_WINDOW_VIOLATION` (range exceeds V1's frequency-dependent cap), or `NOT_FOUND` (bad ID). IMPORTANT — no-fallback rule: if this tool returns an empty `table` (no rows) or an error for the requested period, the history is genuinely unavailable. Do NOT loop fetch_index_data to reconstruct the series. If search_index_datapoints showed `constraints.notes` about choosing rebalancing calendar dates, anchor start_date/end_date using getIndexDescription (INDEX_MASTER_DESCRIPTION: last_rebalancing_date / next_rebalancing_date) instead of inventing "today".MSCI ConnectorMSCIPluginrequiredData & Analytics
- Get Index Dashboardget · Render a visual MCP-app dashboard for a supported dataset. Currently supports dashboard="inclusion_monitor": a single-security Index Inclusion Module (IIM) snapshot (membership & AUM across MSCI World/EM/ACWI families, investability screens, liquidity), given entityId as a numeric MSCI security code. Use get_index_inclusion_insight instead for module-level or multi-security Inclusion Module queries.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Get MSCI Analytics Tools Auth Statusget · Return authentication status and user identity if authenticated.
Returns:
Dictionary with authentication details:
- authenticated: True if user has valid JWT
- msci_user_id: MSCI user ID from JWT claims
- tenants: List of tenant IDs user has access to
- workspace_selected: True if user has a workspace selected
- workspace_id: Current workspace ID (if selected)
If not authenticated, returns authenticated=False with mode indicator.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Get MSCI Analytics Tools PortfolioAI Insights Date Rangeget · Get available data date range for an Insights group.
NOTE: If you have already called list_at_pai_portfolios, start_date and end_date
are already included per portfolio and at the group level in that response —
do NOT call this tool in that case.
Only call this if you need date range without listing portfolios first.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Get MSCI Analytics Tools PortfolioAI Risk Reportget · Fetch a RAW Factor-Risk or Market-Risk data report for a portfolio (data-only, not a summary).
IF THE USER ASKED FOR A SUMMARY, EXPLANATION, OR NARRATIVE of factor risk,
do NOT hand-roll one from this — use `manage_at_workflow(action='start', name='summarize_risk')`
(Factor Risk) or `manage_at_workflow(action='start', name='summarize_risk_mr')` (Market Risk).
report_type and portfolio_name are inferred from data_set_id_hash when omitted.
Returns a markdown report plus meta. Use search_at_pai_portfolio first; pass hash and measure from the same configuration.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Get MSCI Analytics Tools Server Infoget · Return server version and enabled modules.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Get MSCI Private Assets Helpget · Get documentation for MCP tools and modules.
Returns help content aggregated from all registered modules.
Args:
topic: Optional module or tool name to look up. Accepts:
- None: Returns server overview with all modules and tool summaries
- Module name (e.g., "pci"): Returns module overview with tool summaries
- Tool name (e.g., "get_pci_user_profiles"): Returns detailed tool help
Returns:
Help documentation as structured data:
- No argument: Server info, server tools, all modules with tool summaries
- Module name: Module info with tool summaries
- Tool name: Detailed help for the specific tool
Example:
# Get full server overview
get_pa_help()
# Get module overview with tool summaries
get_pa_help(topic="pci")
# Get detailed help for a specific tool
get_pa_help(topic="get_pci_user_profiles")MSCI ConnectorMSCIPluginrequiredData & Analytics
- Get MSCI Private Capital Intel Analysis Contextget · Get reference data needed to build valid PCI universe analytics calls.
Call this before supplying analysis_end_date to get_pci_measure_detail, or
when the user asks which periods are available. The Analytics API only
accepts analysis end dates from a published list that grows every quarter,
so the valid values cannot be assumed.
Args:
action: Which reference dataset to return. Each action names the data
it returns; 'analysis_dates' gives the valid analysis start and end
dates.
Returns:
For 'analysis_dates': valid_analysis_end_dates (quarter-END dates, the
only accepted values for analysis_end_date), valid_analysis_start_dates
(quarter-START dates), the latest end date, both counts and the read
timestamp. The two lists are independent and must not be paired by
position.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Get MSCI Private Capital Intel Measure Detailsget · Get universe analytics benchmarking data for private capital funds.
Most measures return a single as-of-date snapshot in analysis_results.
TWRR_QTD is different: it returns a QUARTERLY TIME SERIES in
time_series_results. Requesting both kinds in one call returns both
datasets side by side; they are not row-comparable and must not be merged.
analysis_start_date and analysis_end_date bound the TWRR_QTD series only.
They never change point-in-time measures. Call
get_pci_analysis_context(action='analysis_dates') to pick real
quarter boundaries.
If this tool returns a parameter_validation_failed error, analyze the included help
content to understand valid values and retry with corrected parameters.
Args:
measures: Comma-separated measure names (defaults to IRR if omitted)
profile_guid: Profile GUID (omit to auto-select)
group_by: Grouping fields (comma-separated)
vehicle_type: Vehicle type filter
geography: Geography filter (hierarchical paths)
industry: Industry filter
asset_class: Asset class filter (hierarchical paths)
vintage: Vintage year filter
leverage: Leverage filter (Fund vehicle only; comma-separated)
seniority: Seniority filter (Fund vehicle only; comma-separated)
market: Market filter (Fund of Funds only; comma-separated)
min_fund_size: Minimum fund size in millions
max_fund_size: Maximum fund size in millions
pooled_currency: Currency for the pooled/aggregate result. Defaults
to USD when omitted. 'Local' is not allowed.
individual_currency: Currency for percentile/individual-fund
results. Defaults to Local (each fund's own reporting
currency) when omitted.
analysis_start_date: YYYY-MM-DD. Earliest quarter in the TWRR_QTD
series (inclusive). Time series only. Omit for full history.
analysis_end_date: YYYY-MM-DD. Latest quarter in the TWRR_QTD series
(inclusive). TIME SERIES ONLY -- has no effect on point-in-time
measures, which always use the API's own as-of date.
Returns:
Dictionary with analysis_results (point-in-time measures),
time_series_results (TWRR_QTD quarters), dates_applied, profile info
and llm_response_footer. Each results block is present only when the
corresponding measures were requested.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Get MSCI Private Capital Intel User Profilesget · Get PCI-enabled profiles for the authenticated user.
Returns:
Dictionary with profiles list, profile_count, access_status, and optional environment.
On Platform API failure, returns status api_error with error and user_guidance
(same shape as get_measure_detail downstream failures).MSCI ConnectorMSCIPluginrequiredData & Analytics
- Get MSCI Real Assets Index Catalogget · ROUTING — Real Assets direct property & fund data. Trigger: 'property index', 'real estate index', 'IPD', 'direct property', 'capital growth', 'income return', 'standing investments', '[Country] Quarterly/Annual Property Index'. NOT for equity indices, factor indices, or listed portfolios (use AIIndexInsights/TPM).
Prefer ``get_rai_metadata`` first; use this tool for full lists, debugging, or when
metadata returns poor candidates.
Load ``instructions.md`` first via ``get_rai_reference_docs(doc_name="instructions")`` if not already in context.
TOKEN COST GUIDE — call only what you need:
• ``datasets`` → ~12,000 tokens (fallback when metadata fails for dataset)
• ``measures`` → ~4,000 tokens (fallback when metadata fails for measures)
• ``segmentations`` → ~23,000 tokens ⚠️ MOST EXPENSIVE. Only when metadata
returned zero segmentation candidates AND user asked for a specific segmentation.
• ``segmentation_nodes`` → <500 tokens (only after segmentation_id is known)
Args:
resource: One of: ``datasets``, ``measures``, ``segmentations``, ``segmentation_nodes``.
product_ids: For ``measures``: optional comma-separated product IDs.
product_id: For ``segmentations`` / ``segmentation_nodes``: optional product ID.
as_of_date: Optional as-of date (YYYY-MM-DD).
segmentation_id: Required for ``segmentation_nodes``. Simple (e.g. ``"2"``) or
cross-segmentation (e.g. ``"264::2"``).
measure_ids: Comma-separated IDs → full detail objects; omit → trimmed list.
dataset_ids: Comma-separated IDs → full detail objects; omit → trimmed list.
search_text: For ``segmentation_nodes`` only: optional name filter.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Get MSCI Real Assets Index Metadataget · ROUTING — Real Assets direct property & fund data. Trigger: 'property index', 'real estate index', 'IPD', 'direct property', 'capital growth', 'income return', 'standing investments', '[Country] Quarterly/Annual Property Index'. NOT for equity indices, factor indices, or listed portfolios (use AIIndexInsights/TPM).
DEFAULT: when the user has not specified frozen or unfrozen, always use the unfrozen (live) dataset (dataSource: "LOCKED").
Load ``instructions.md`` first via ``get_rai_reference_docs(doc_name="instructions")`` if not already in context.
Fuzzy-match datasets, segmentations, segmentation nodes, and measures in one call.
All parameters use **empty string** defaults (not ``null``) — this keeps the JSON Schema
as plain ``string`` types and avoids ``anyOf[string, null]`` serialization issues.
Alternatively pass **only** ``populate_filters_json`` as a JSON object string (easier
when the MCP host mis-serializes multi-field arguments).
Args:
datasets: Comma-separated dataset names. e.g. "UK Quarterly", "Germany Annual"
segmentations: Comma-separated segmentation axis names; ``""`` when not needed.
measures: Comma-separated measure names; ``""`` when not needed.
segmentation_nodes: Comma-separated leaf node names to fuzzy-search alongside
``segmentations``; ``""`` when not needed. When empty, matches legacy populate
behaviour (no ``segmentationNodes`` in the API request).
populate_filters_json: Optional JSON string overriding the above, e.g.
``{"datasets":"UK Quarterly","segmentations":"Office","measures":"Total Return"}``.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Get MSCI Real Assets Index Reference Documentationget · ROUTING — Real Assets direct property & fund data. Trigger: 'property index', 'real estate index', 'IPD', 'direct property', 'capital growth', 'income return', 'standing investments', '[Country] Quarterly/Annual Property Index'. NOT for equity indices, factor indices, or listed portfolios (use AIIndexInsights/TPM).
Get reference documentation and server instructions for Real Assets MCP.
IMPORTANT — CALL ON FIRST CONNECTION: When ``instructions.md`` is not already in your
context from the host, your **first** Real Assets MCP call MUST be this tool with
``doc_name="instructions"`` to load behavioural rules, query workflows, and domain context.
Do **not** call ``get_rai_catalog``, ``get_rai_metadata``, or ``get_rai_results``, and do
not answer substantive Real Assets user questions until you have **read** that document.
Args:
doc_name: Name of the document to retrieve. Valid values:
- "instructions" - Server instructions. MUST be loaded once at session start (before other ``get_rai_*`` tools) unless host-preloaded.
- "api_payload_validation" - Complete API endpoint contracts
- "query_builder_rules" - Full business rules and constraints
- "query_builder_data_flow" - UI portal data flow patterns
- "nlp_measure_synonym_map" - NLP term to measure/module translation table
- "nlp_index_and_time_synonyms" - Region/country to dataset mapping + time synonyms
- "" or "list" - Returns list of available documents
Returns:
Document content and metadata, or list of available documents.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Get MSCI Real Assets Index Resultsget · ROUTING — Real Assets direct property & fund data. Trigger: 'property index', 'real estate index', 'IPD', 'direct property', 'capital growth', 'income return', 'standing investments', '[Country] Quarterly/Annual Property Index'. NOT for equity indices, factor indices, or listed portfolios (use AIIndexInsights/TPM).
Execute a custom query with explicit parameters (advanced use).
Load ``instructions.md`` first via ``get_rai_reference_docs(doc_name="instructions")`` if not already in context.
NOTE: This is the primary execution tool. Use get_rai_metadata first to
resolve dataset/segmentation/measure IDs, then call this with the built payload.
⚠️ CUSTOM QUERIES NOT SUPPORTED: Queries requiring background processing
(custom datasets, custom filters, cumulative aggregation, etc.) will be rejected.
Args:
result_request_json: JSON string containing the ResultRequestModel with:
- datasets: List of dataset configurations (mandatory)
- measureFunctionFilterDetails: Measures with aggregation settings (mandatory)
- segmentationIds: List of segmentation IDs (mandatory)
- segmentationNodeIds: List of segmentation node IDs (mandatory)
- reportingFrequencyId: Frequency (1=monthly, 3=quarterly, 12=annual)
- startDateNumber: Start date in YYYYMM format
- endDateNumber: End date in YYYYMM format
- mcpResponseFilterSegmentationNodeIds: Optional MCP-only list of node id strings.
When set, the tool removes this key before calling the API and post-filters nested
result lists whose rows expose a node id, keeping only matching ids. Omit for
legacy behaviour (full API payload returned).
Returns:
Dictionary with query results.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Get MSCI Sustainability and Climate API integration help [Beta]get · Use this tool ONLY when the user asks about MSCI Sustainability & Climate Data APIs, needs API endpoint discovery, authentication/OAuth setup guidance, API specifications, client boilerplate code, or code generation to call those endpoints. This tool does not invoke live APIs. Do NOT use for S&C data values, methodology, factor discovery, or taxonomy — use query_sustainability_climate_taxonomy and query_sustainability_climate_data instead.
Operations:
esg_api_search — Finds the most relevant API endpoints (URL, method, parameters, and reasoning) and recommends calling the same tool with operation_id: esg_api_docs for detailed endpoint documentation and boilerplate code, as well as query_sustainability_climate_taxonomy with relevant operation IDs for factor discovery and taxonomy queries.
esg_api_docs — Primary source for curated MSCI documentation, API specifications and boilerplate code. Single call can mix types. Returns relevant auth guidelines for OAuth setup, boilerplate code to invoke endpoints, samples, or full API specs including schemas, parameters, errors, and examples.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Get MSCI Total Plan Manager Contextget · Discover the funds, portfolios, dates, dimensions, and fundamentals behind
TPM (Caissa) holdings and exposure analytics, and resolve the things a user
names (a fund, a portfolio, a sector, an issuer, a metric) into the numeric
ids that get_tpm_transparency_analysis needs. Don't guess ids — look them up here.
Prerequisite: first call get_pa_help(topic='get_tpm_context') and pass its
tool_identifier on this call.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Get MSCI Total Plan Manager Loginsget · Manual backup tool for client discovery. NOT needed in normal workflows.
All other TPM tools auto-resolve the client invisibly. This tool exists only for:
- When the user explicitly asks to see their available clients
DO NOT call this tool to "lock" the client before get_tpm_context or get_tpm_transparency_analysis.
When the user names a client (e.g. "TPM Test") and asks for funds, call
get_tpm_context(action="entities", entity_type="Fund") directly — do not call this tool first.
When a tool returns client_selection_required and the user confirms, retry
THAT tool with login_username — do not call this tool to lock.
Args:
login_username: When provided, locks this client for the session (used
after user confirms a multi-client selection). When omitted,
returns the list of accessible clients.
Returns:
Dictionary with clients list and count, or lock confirmation.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Get MSCI Total Plan Manager Transparency Analysisget · Run transparency/exposure and characteristics analysis on a fund or portfolio
in TPM (Caissa): holdings decomposed across dimensions such as sector, asset
class, geography, issuer, currency, and underlying securities, and how those
holdings score on security characteristics.
It covers two analytical families. Transparency/exposure gives exposure by
dimension (sector, geography, asset class, issuer, currency, security id) as
long/short/net/gross and % of total. Characteristics gives exposure-weighted
fundamentals (e.g. P/E, market cap, yield, duration) rolled up to the fund or
portfolio level.
Prerequisite: first call get_pa_help(topic='get_tpm_transparency_analysis')
and pass its tool_identifier on this call.MSCI ConnectorMSCIPluginrequiredData & Analytics
- List MSCI Analytics Tools PortfolioAI Insights Groupslist · List all available Insights portfolio groups with portfolio counts.
Use this to discover group names for list_at_pai_portfolios and query_at_pai_agent.
Returns JSON with groups array (name, portfolio_count), total counts, and usage notes.MSCI ConnectorMSCIPluginrequiredData & Analytics
- List MSCI Analytics Tools PortfolioAI Insights Portfolioslist · List all portfolios in a specific Insights group.
Use after list_at_pai_groups to see portfolios available in a group for query_at_pai_agent queries.
Returns JSON with group name, portfolios array with full metadata (portfolio_name, portfolio_id,
data_set_id, benchmark_name, report_type, measure, start_date, end_date), count, and
group-level start_date and end_date covering the full date range across all portfolios.
Date range is already included — do NOT call get_at_pai_date_range after this.MSCI ConnectorMSCIPluginrequiredData & Analytics
- List MSCI Index Methodologieslist · List MSCI Index methodology documents available as of a given date. Returns `{ as_of_date, items: [{ code, name }] }`. Use `code` with search_index_methodology to search a specific methodology, or call search_index_methodology_stack with an `index_code` to span the full stack that applies to one index.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Manage MSCI Analytics Tools Workflowmanage · List, start, advance, check status on, or abandon a workflow session. Also supports a stateless single-step fetch (name + step, no action).
Available workflows:
- `risk_dashboard`: Build an interactive React risk dashboard for a portfolio. Use this when the user asks for a dashboard, visualization, or interactive view of portfolio risk. Runs the same MSCI analysis and summary methodology as `summarize_risk`, then renders it as charts and KPI cards.
- `risk_dashboard_mr`: Build an interactive React dashboard for a portfolio's MARKET RISK (VaR / time-series). This is the MR counterpart to `risk_dashboard` (which is Factor Risk only). Use this when the user asks for a dashboard, visualization, or interactive view and the configuration's report_type is Market Risk. Runs the same MSCI MR analysis and summary methodology as `summarize_risk_mr`, then renders it as charts and KPI cards.
- `summarize_risk`: START HERE for any request to summarize, explain, analyze, or narrate a portfolio's risk (tracking error or total risk). This is the correct, MSCI-sanctioned path — do NOT hand-roll a summary from raw data. The workflow fetches the risk report, gathers news context, and applies the required MSCI analysis and summary methodology that is NOT derivable from the raw data tables alone. Use `get_at_pai_risk_report` directly only when the user wants raw risk numbers, not a summary or narrative. This workflow is **Factor Risk only** (tracking error / total risk); for Market Risk (VaR / time-series) use `summarize_risk_mr` instead.
- `summarize_risk_mr`: START HERE to summarize, explain, analyze, or narrate a portfolio's MARKET RISK (VaR / time-series). This is the MR counterpart to `summarize_risk` (which is Factor Risk only). Use this when the configuration's report_type is Market Risk. Do NOT hand-roll a summary from raw data.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Query MSCI Analytics Tools PortfolioAI Insights Agentquery · Query the AI Portfolio Insights agent with natural language questions about portfolios.
For a structured summary, explanation, or narrative of portfolio RISK
specifically, prefer the `summarize_risk` workflow — call
`manage_at_workflow(action='start', name='summarize_risk')` — it applies the
required MSCI analysis and summary methodology. Use this agent for ad-hoc questions,
performance, attribution, factor exposures, or plotting requests.
The agent analyzes portfolio risk, performance, attribution, and factor exposures.
Returns JSON with response (text), context_used, and when charts are generated: chart images as separate MCP image content blocks (no artifact URLs), charts_included count, and a required_action instructing you to create a React artifact from the attached images. You MUST follow required_action when present.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Query MSCI Sustainability and Climate data [Beta]query · Preferred authoritative tool for in-scope ESG and Sustainability & Climate (S&C) data.
Typical examples (by product):
- ESG Controversies: "List active ESG controversy cases for Shell."
- Business Involvement Screening: "What is the tobacco revenue exposure for this issuer?"
- ESG Ratings: "What is Apple's MSCI ESG rating for the latest period?"
operation values
-`fetch_data` - Retrieves actual S&C data records (not metadata or methodology explanations) for the user query, scoped to the entitled product subscriptions.
Strict Guidelines:
- Use this tool when the user asks for ESG or S&C data values, records, counts, lists, comparisons, issuer-level results, or other product-backed outputs for supported products: ESG Controversies, Business Involvement Screening, or ESG Ratings. Skip for methodology-only intent.
- Route generally phrased ESG or S&C questions here even when the user does not explicitly mention "MSCI".
- Do not fall back to **web search or training data** unless the tool indicates request is unsupported or out of scope.
- When the response includes display_config.verbatim_columns, show the values from those columns exactly as they appear in table_data. Do not truncate, summarize, paraphrase, translate, reformat, or add/remove prefixes, suffixes.
- When calling fetch_data, never copy, paraphrase, or reference factor names, codes, or labels from shortListedFactors into userQuery. userQuery must reflect only the user's original question.
- Invoke the tool utmost **twice** to fulfill the complete request, refining across iterations, if needed within the same supported ESG and S&C scope.
- For ESG Ratings requests that explicitly ask for "drill-down" or
"drilldown" scores, first call `query_sustainability_climate_taxonomy` with operationId = `semantic_search_documents` to identify the MSCI-defined drill-down score structure/components. Then call
`semantic_search_factors` to resolve exact factor names before calling `query_sustainability_climate_data`.
- shortListedFactors: Factors relevant to the user query from tool `query_sustainability_climate_taxonomy` with operationId `semantic_search_factors`; do not invent or assume factor_names. If no factor names are resolved, pass it as empty.
- userQuery: Rewrite the user's original question as a clean standalone query using only the words and intent the user supplied. Stop writing when the user's
intent is fully captured and enriched — do not expand or supplement with any additional terms.
- Presenting the response: Present ONLY what the tool returned in `messages`, `query_explanation`, and `table_data`. Treat these
fields as the complete and authoritative answer. You may lightly rephrase or reorder them to read naturally and to directly address
the user's question, but the result MUST remain a faithful restatement of the returned content. You MUST NOT add anything that is not
present in the tool response, including: facts, figures, dates, factor names, or domain terminology; interpretations or explanations of
what a value, score, rating, band, or scale "means"; qualitative characterizations or judgements (e.g. "average", "unexceptional",
"strong", "poor", "well-managed"); peer, sector, or historical comparisons; or any added background, context, or caveats. If the user
asks what a returned value means and the response does not explain it, say that explanation is not available from this tool and offer to
look it up via `query_sustainability_climate_taxonomy` — do NOT explain it from your own knowledge. Never substitute or supplement the tool's values with content from your own training data or
general knowledge. When a characterization or definition DOES appear in the response, you may relay it but attribute it to MSCI
(e.g. "per MSCI S&C data, ...").MSCI ConnectorMSCIPluginrequiredData & Analytics
- Query MSCI Sustainability and Climate taxonomy [Beta]query · Preferred authoritative tool for in-scope ESG and Sustainability & Climate (S&C) methodology, taxonomy, and factor-discovery questions served by this MCP server; use before web search.
Use this tool when the user asks about ESG or S&C methodology, factor discovery, taxonomy tagging, document retrieval,
or other related in-scope ESG or S&C topics covered by this server.
Route generally phrased ESG or S&C questions here even when the user does not explicitly mention "MSCI".
Do not use web search for those requests unless this tool returns no relevant coverage or the request is outside the
supported ESG and S&C domains.
Typical examples:
- "How is this score or indicator calculated?"
- "Which factor matches a question about active cases by pillar?"
- "Find methodology text for this metric or indicator."
Sustainability & Climate taxonomy (S&C): set operationId to`get_taxonomy_tags_for_request`, `semantic_search_documents` or `semantic_search_factors`
1) operationId:`get_taxonomy_tags_for_request` Classify and tag an ESG- or S&C-related query to return the most relevant taxonomy tag paths.
Each tag's ancestors are implicitly relevant - returning a child tag means its parent is also a valid filter.
2) Invoke tool `query_sustainability_climate_taxonomy` with `operationId` `semantic_search_documents`.
Search ESG and S&C methodology documentation by semantic similarity. Returns document chunks for a query, optionally filtered by taxonomy tags. From all hits, shortlist only chunks that are directly relevant and sufficient to answer the user query—exclude semantically close but unrelated passages; do not treat tangential matches as authoritative methodology support.
This server covers a subset of in-scope ESG and S&C documentation and taxonomy domains, with partial coverage for some areas.
If your search does not find information for a topic, you may assume that the documentation does not currently cover it.
3) operationId:`semantic_search_factors` Search for an ESG or S&C factor, indicator, coefficient or other data point by name and description. Only factors from the ESG and S&C domains are covered.
Presenting the response: Present ONLY the content returned by this tool (its `tags`, `documents`, and factor `results` with their
names and descriptions). Quote or faithfully restate the returned methodology, definitions, and factor descriptions. Do NOT add
interpretation, examples, qualitative judgements, or explanations of what a metric, score, rating, band, or scale "means" beyond what the
returned text itself states; do NOT extend a returned scale or definition with your own characterizations (e.g. describing a mid-scale
value as "average" or "unexceptional"). If the returned text does not answer the user's question, say so rather than filling the gap from
your own training data or general knowledge. Attribute relayed definitions to MSCI (e.g. "per MSCI methodology, ...").MSCI ConnectorMSCIPluginrequiredData & Analytics
- Read MSCI Analytics Tools Guidanceread · IMPORTANT: Call this tool FIRST before using any other analytics tool.
Returns guidance on how to use all the tools available on this server —
tool sequencing, workflow patterns, module documentation, and
cross-module integration rules for all currently active modules.MSCI ConnectorMSCIPluginrequiredData & Analytics
What is Tool Explorer?
Tool Explorer indexes the callable tool names and descriptions attached to public registry profiles. It is useful for seeing what agents can actually invoke, not just which profile exists.
How do category and verb filters work?
Category filters use the live registry category rollup. Verb filters use the public tool insights rollup, so the page stays backed by the same read models as the tracker charts.
Why do auth requirements matter?
Auth requirements show whether a tool is likely usable without account connection, requires authentication, is private, or is unknown in the current snapshot.