神策Wave数据治理（Wave-catalog-governance）

Maintain low-risk Sensors Wave Catalog metadata for existing events, event properties, and user properties. Use when updating display names,descriptions, event trigger conditions, platform tags, or example values.Do not use for renaming technical names, changing data types, deleting metadata, merging duplicates, or designing new tracking plans.

Wave Catalog Governance

Goal

Maintain documentation-grade Catalog metadata for existing events and properties using the current MCP write tools.

Tools

Discover current values: list_projects, list_events, list_event_properties, list_user_properties
Update events: update_event_metadata
Update event properties: update_event_property_metadata
Update user properties: update_user_property_metadata
Bulk context: read resource wave://catalog/summary when available

Writable Fields

Event: display_name, description, trigger_condition, platforms
Event property: display_name, description, example_value
User property: display_name, description, example_value

Workflow

Pass the project gate before any other project-level MCP call: list_projects, show project_id | name, and wait for a numeric project_id. Only skip a new selection if the user already fixed this conversation to one project, or explicitly says to keep the current project without switching. Never silently choose a project.
Query the current Catalog objects by id, technical name, or search keyword.
Prepare a change list with object type, id/name, current value, proposed value, and reason.
Ask for confirmation before any update call.
Include expected_name when updating by id or search-derived match to prevent wrong-object edits.
Run the correct update tool.
Re-query the changed object and report confirmed final values.

Boundaries

Do not read or update Catalog objects before the user selects a project_id.
Do not rename technical names.
Do not change data types.
Do not delete, archive, or merge metadata.
Do not create new events/properties or Tracking Plans.
Do not claim future governance operations are available until the MCP exposes corresponding tools.

If the user asks for a non-writable operation, explain the current tool boundary and, if appropriate, route to wave-tracking for redesign or to wave-product-help for product guidance.

Output

Return:

Changes applied
Objects skipped and why
Any values that still need user confirmation
Suggested next step, if the requested governance cannot be completed with current MCP tools