Inspect a dimension

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.
• {{dimension_id}} Stable dimension ID, or a unique name to resolve.

Prompt

In {{workspace_id}} / {{application_id}}, discover the scoped catalog.
Use read_v2_program with metadata.dimension.resolve and reference {{dimension_id}}, then metadata.member.list and metadata.relationship.list for the resolved ID.
For members, use nextAfterMemberId as afterMemberId and retain expectedMetadataRevision from the first page. For relationships, send only cursor from the previous nextCursor.
For a named attribute, use metadata.attribute-value.read with its scope, dimensionId, attributeId, and objectId. Check present and report the typed value.
Report the returned members, relationships and attribute values at one metadata revision.
Stop if the dimension is missing or ambiguous.
Do not edit the dimension.

Example inputs

In the disposable Operating Data Cube, send each argument object below with its named function. Page the member and relationship results. Expect the active InputA member, the Metrics to InputA relationship, and the named Behavior value Input.

{
  "metadata.dimension.resolve": {"reference":"Account"},
  "metadata.member.list": {"dimension":"Account","limit":2},
  "metadata.relationship.list": {"dimension":"Account","status":"Active","limit":2},
  "metadata.attribute-value.read": {"scope":"Member","dimensionId":"Account","attributeId":"Behavior","objectId":"InputA"}
}

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