MCP Standard Tools 1.0.5–1.0.6: SuiteQL Metadata Tool and Consolidated Subsidiary Support

What changed

Version 1.0.6 — SuiteQL metadata and consolidated subsidiaries

New tool: ns_getSuiteQLMetadata — Returns field-level metadata for any record type accessible via SuiteQL. Pass a record type to get its fields and relationships; omit the parameter to get a list of all supported record types. The existing ns_runCustomSuiteQL tool now calls ns_getSuiteQLMetadata internally before building queries, so generated SuiteQL will only reference valid fields and joins.

Consolidated and context subsidiaries in ns_getSubsidiaries — The tool now returns three flavors of subsidiary:

• Individual — positive internal ID.
• Consolidated — negative internal ID. When passed to ns_runReport, the report aggregates data for the selected subsidiary and all its children.
• Context — negative internal ID. Reports run against a context subsidiary show data for every child subsidiary you can access, denominated in the context subsidiary's currency.

Any tool or integration that consumes subsidiary IDs from ns_getSubsidiaries must now handle negative IDs. Passing a negative ID to a tool that expects only individual subsidiaries will produce unexpected results.

Version 1.0.5 — Report tool enhancements

• ns_listAllReports now includes custom reports in its response, not just standard reports.
• ns_runReport gains a subsidiaryId parameter. This parameter is required when the target report uses a subsidiary filter and the account has subsidiaries enabled.
• New tool ns_getSubsidiaries returns the subsidiary list available for report filtering.
• Report output now respects currency: multi-subsidiary accounts use the subsidiary's currency; single-entity accounts use the base currency from the Company Information page.

What to do

1. Update the SuiteApp. Confirm you are on MCP Standard Tools version 1.0.6 (or later) via Customization > SuiteBundler > Search & Install Bundles.
2. Handle negative subsidiary IDs. If you have scripts or integrations that consume the output of ns_getSubsidiaries, add logic to distinguish individual (positive), consolidated (negative), and context (negative) IDs. Oracle's documentation does not clarify how to differentiate consolidated from context beyond the subsidiary hierarchy — verify behavior in your sandbox.
3. Supply subsidiaryId for subsidiary-filtered reports. Any automation calling ns_runReport on a report with a subsidiary filter will now fail or return incorrect data if subsidiaryId is omitted in a multi-subsidiary account. Audit existing calls.
4. Leverage ns_getSuiteQLMetadata for validation. If you build SuiteQL dynamically, call this tool first to confirm field names and join paths rather than hard-coding them. This is especially useful when targeting custom record types whose schema can change between environments.
5. Test currency output. If downstream systems parse monetary values from report results, confirm the currency matches expectations after the update — reports now inherit the subsidiary's currency rather than a static default.