Inspect an application’s structure

Replace the placeholders with values from your own authorized scope before copying this prompt into an MCP client.

Inputs

• {{workspace_id}} Stable workspace ID.
• {{application_id}} Stable application ID.
• {{max_pages}} Maximum number of dimension pages to fetch.

Prompt

Use list_v2_functions for {{workspace_id}} / {{application_id}} and check the returned listener scope. Use read_v2_program with application.state.read and metadata.dimension.list.
List dimension IDs, names and statuses alongside the application revisions. Report the function catalog separately from the model's dimensions.
When hasMore is true, pass nextAfterDimensionId as afterDimensionId and metadataRevision as expectedMetadataRevision. Keep the same limit and fetch at most {{max_pages}} pages. Report whether the result covers all dimensions in scope.
If scope or access cannot be verified, report the error and stop without making changes.

Example inputs

In the populated Operating Data Cube sample, use application_id operating-cube and max_pages 5. Start metadata.dimension.list with the arguments below. Confirm that the Account dimension is present and every dimension page has the same metadata revision. A blank application can expose metadata functions and return an empty dimension list.

{"limit":2}

Tools used include list_v2_functions, read_v2_program. See the module guidelines and tool index.