concert-operate-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONCERT_BASE_URL | Yes | Base URL of your Concert Operate instance, e.g. https://cpd.example.com | |
| CONCERT_CPD_USER | Yes | Cloud Pak for Data username | |
| CONCERT_TENANT_ID | No | Tenant ID. The default is the standard value shipped with every Concert Operate installation. Override only if your instance uses a custom tenant ID. | cfd95b7e-3bc7-4006-a4a8-a73a79c71255 |
| CONCERT_CPD_PASSWORD | Yes | Cloud Pak for Data password |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create-eventB | Create a new event in Concert Operate. |
| create-alertC | Create a new alert in Concert Operate. |
| get-alertsA | Retrieve all alerts, optionally filtered. Severity values: 6=Critical, 5=Major, 4=Minor, 3=Warning, 2=Information, 1=Indeterminate. |
| get-alertA | Get a single alert by its ID. |
| update-alertB | Update specific fields of an alert by ID. |
| bulk-update-alertsA | Bulk-update all alerts matching a filter expression. |
| get-alert-timelineB | Get all timeline entries for an alert. |
| add-alert-commentA | Add a comment (timeline entry) to an alert. |
| get-alert-insightsA | Retrieve all insights for an alert, optionally filtered by insight type. |
| create-alert-insightC | Add a new insight to an alert. |
| get-alert-insightC | Get a specific insight on an alert by insight ID and type. |
| delete-alert-insightB | Delete a specific insight from an alert. |
| get-incidentsA | Retrieve all incidents. |
| get-incidentA | Get a single incident by its ID. |
| update-incidentC | Update specific fields of an incident. |
| get-incident-timelineB | Get all timeline entries for an incident. |
| add-incident-commentA | Add a comment to an incident timeline. |
| get-policiesC | List all policies. |
| get-policyA | Retrieve a single policy by ID. |
| create-policyC | Create a new policy. |
| create-policies-bulkB | Create multiple policies in a single request. |
| update-policyB | Partially update a policy by ID (PATCH). |
| replace-policyA | Replace an entire policy by ID (PUT). |
| delete-policyB | Delete a policy by ID. |
| get-policy-execution-statusC | Retrieve execution status for a policy. |
| get-policy-timelineB | Retrieve timeline entries for a policy. |
| get-runbooksA | List all runbooks. |
| get-runbookB | Get a runbook by ID. |
| create-runbookC | Create a new runbook. |
| update-runbookC | Update an existing runbook. |
| delete-runbookC | Delete a runbook. |
| get-runbook-versionsB | Get all versions of a runbook. |
| get-runbook-versionB | Get a specific version of a runbook. |
| get-runbook-referencesC | Get references for a runbook. |
| get-runbook-statisticsC | Get execution statistics for a runbook. |
| execute-runbookC | Execute a runbook (fire-and-forget or synchronous). |
| get-runbook-executionsB | Get all executions for a runbook. |
| get-runbook-executionB | Get a specific runbook execution by instance ID. |
| update-runbook-executionC | Update the status or details of a runbook execution. |
| delete-runbook-executionC | Delete a runbook execution record. |
| get-algorithmsA | List all registered algorithms. |
| get-algorithmB | Get a specific algorithm by name. |
| register-algorithmC | Register a new algorithm with the AI platform. |
| unregister-algorithmC | Unregister an algorithm by name. |
| get-training-definitionsA | List all training definitions. |
| get-training-definitionB | Get a specific training definition by name. |
| create-training-definitionC | Create a new training definition. |
| update-training-definitionD | Update a training definition. |
| delete-training-definitionC | Delete a training definition. |
| get-training-statusA | Get the latest training run status. |
| start-trainingC | Start a training run. |
| get-precheck-statusA | Get the latest precheck run status. |
| start-precheckD | Start a precheck run. |
| stop-precheckA | Stop the current precheck run. |
| get-trained-model-versionsA | List all trained model versions. |
| get-trained-model-versionB | Get a specific trained model version. |
| delete-trained-model-versionC | Delete a trained model version. |
| create-metering-jobC | Create a new metering job. |
| get-metering-jobC | Get complete information for a metering job. |
| get-metering-job-statusC | Get job status only for a metering job. |
| get-metering-job-resultC | Get job result only for a metering job. |
| list-metering-resourcesC | List metering resources with pagination and filtering. |
| get-metering-aggregate-statsB | Get aggregate resource stats for a date range. |
| get-my-preferencesA | Retrieve the current user's preferences. |
| upsert-my-preferenceB | Create or update a preference for the current user. |
| delete-my-preferenceA | Delete a preference by key for the current user. |
| admin-get-all-preferencesB | Admin: retrieve all user preferences. |
| admin-get-user-preferencesC | Admin: retrieve preferences for a specific user. |
| admin-get-user-preferenceB | Admin: retrieve a specific preference by key for a user. |
| admin-upsert-user-preferenceC | Admin: create or update a preference for a specific user. |
| admin-delete-user-preferenceA | Admin: delete a preference by key for a specific user. |
| admin-delete-all-user-preferencesB | Admin: delete all preferences for a specific user. |
| get-automation-toolsA | List all runbook automation tools. |
| get-automation-toolC | Get a specific runbook automation tool. |
| create-automation-toolC | Create a new runbook automation tool. |
| update-automation-toolD | Update a runbook automation tool. |
| delete-automation-toolC | Delete a runbook automation tool. |
| get-menusA | List all UI menus. |
| get-menuC | Get a specific UI menu. |
| create-menuC | Create a new UI menu. |
| update-menuC | Update a UI menu. |
| delete-menuC | Delete a UI menu. |
| get-viewsA | List all UI views. |
| get-viewC | Get a specific UI view. |
| create-viewC | Create a new UI view. |
| update-viewC | Update a UI view. |
| delete-viewB | Delete a UI view. |
| check-view-name-existsC | Check whether a view name exists. |
| get-viz-filtersA | List all visualization filters. |
| get-viz-filterB | Get a specific visualization filter. |
| create-viz-filterC | Create a new visualization filter. |
| update-viz-filterC | Update a visualization filter. |
| delete-viz-filterC | Delete a visualization filter. |
| delete-viz-filters-bulkB | Delete multiple visualization filters. |
| check-viz-filter-name-existsC | Check whether a visualization filter name exists. |
| backup-topology-ui-configB | Backup the topology UI configuration. |
| restore-topology-ui-configB | Restore the topology UI configuration from a backup. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 97 tools
Most tools follow a clear resource+action pattern, making them distinct. However, some tools like get-metering-job, get-metering-job-status, and get-metering-job-result provide overlapping views of the same entity, which could cause confusion.
The naming convention is strongly consistent, using lowercase verb-noun pairs with hyphens (e.g., create-event, get-alerts, update-policy). Minor deviations like the admin- prefixed tools (admin-get-user-preferences) are systematic and do not undermine overall coherence.
With 97 tools, this server is massively over-scoped. It will overwhelm agents with too many options and consume excessive context, making selection and reasoning difficult. The server should be decomposed into smaller, focused servers.
The tool surface is remarkably comprehensive across many modules (alerts, policies, runbooks, training, etc.), with full CRUD where appropriate. Some gaps exist, such as no delete-alert or create/delete-incident, but overall coverage is strong for the apparent domain.