MCP-Ambari-API

Unified configuration introspection tool (supersedes get_configurations & list_configurations & dump_all_configurations).

Modes:

1. Single type values: specify config_type=

2. Bulk list (optionally narrowed by service_filter substring in type name)

3. Filtering keys/types via filter substring

Args: config_type: focus on one type's latest tag (other bulk params ignored except filter on keys) service_filter: substring to restrict bulk types (ignored if config_type provided) filter: substring applied to type names OR property keys summarize: bulk mode summary lines only (counts + sample keys, forces include_values False) include_values: include key=value pairs (bulk/full mode only) limit: max number of types to output in bulk mode (0 = unlimited) max_chars: truncate final output if exceeds

Retrieves basic information for an Ambari cluster.

[Tool Role]: Dedicated tool for real-time retrieval of overall status and basic information for an Ambari cluster.

[Core Functions]:

• Retrieve cluster name, version, provisioning state, and security type

• Provide formatted output for LLM automation and cluster monitoring

[Required Usage Scenarios]:

• When users request cluster info, status, or summary

• When monitoring cluster health or auditing cluster properties

• When users mention cluster overview, Ambari cluster, or cluster details

Returns: Cluster basic information (success: formatted info, failure: English error message)

Retrieves currently active (in progress) requests/operations in an Ambari cluster. Shows running operations, in-progress tasks, pending requests.

[Tool Role]: Dedicated tool for monitoring currently running Ambari operations

[Core Functions]:

• Retrieve active/running Ambari operations (IN_PROGRESS, PENDING status)

• Show real-time progress of ongoing operations

• Monitor current cluster activity

[Required Usage Scenarios]:

• When users ask for "active requests", "running operations", "current requests"

• When users ask for "request list", "operation list", "task list"

• When users want to see "current tasks", "running tasks", "in progress operations"

• When users mention "running", "in progress", "current activity"

• When users ask about Ambari requests, operations, or tasks

• When checking if any operations are currently running

Returns: Active requests information (success: active request list, failure: error message)

Retrieves the list of services with status in an Ambari cluster.

[Tool Role]: Dedicated tool for real-time retrieval of all running services and basic status information in an Ambari cluster

[Core Functions]:

• Retrieve cluster service list with status via Ambari REST API

• Provide service names, current state, and cluster information

• Include detailed link information for each service

• Display visual indicators for service status

[Required Usage Scenarios]:

• When users mention "service list", "cluster services", "Ambari services"

• When cluster status check is needed

• When service management requires current status overview

• When real-time cluster information is absolutely necessary

[Absolutely Prohibited Scenarios]:

• General Hadoop knowledge questions

• Service installation or configuration changes

• Log viewing or performance monitoring

• Requests belonging to other cluster management tools

Returns: Cluster service list with status information (success: service list with status, failure: error message)

Retrieves the status information for a specific service in an Ambari cluster.

[Tool Role]: Dedicated tool for real-time retrieval of specific service status and state information

[Core Functions]:

• Retrieve specific service status via Ambari REST API

• Provide detailed service state information (STARTED, STOPPED, INSTALLING, etc.)

• Include service configuration and component information

[Required Usage Scenarios]:

• When users ask about specific service status (e.g., "HDFS status", "YARN state")

• When troubleshooting service issues

• When monitoring specific service health

Args: service_name: Name of the service to check (e.g., "HDFS", "YARN", "HBASE")

Returns: Service status information (success: detailed status, failure: error message)

Retrieves detailed components information for a specific service in the Ambari cluster.

[Tool Role]: Dedicated tool for retrieving service component details and host assignments.

[Core Functions]:

• List all components for a service, including state and category

• Show host assignments and instance counts

• Provide formatted output for LLM automation and troubleshooting

[Required Usage Scenarios]:

• When users request service component details or host info

• When troubleshooting service health or scaling

• When users mention component list, host assignments, or service breakdown

Args: service_name: Name of the service (e.g., "HDFS", "YARN", "HBASE")

Returns: Service components detailed information (success: formatted list, failure: English error message)

Retrieves detailed status and configuration information for a specific service in the Ambari cluster.

[Tool Role]: Dedicated tool for retrieving comprehensive service details, including state, components, and configuration.

[Core Functions]:

• Retrieve service state, component list, and configuration availability

• Provide formatted output for LLM automation and troubleshooting

[Required Usage Scenarios]:

• When users request detailed service info or breakdown

• When troubleshooting service health or auditing service setup

• When users mention service details, service summary, or configuration status

Args: service_name: Name of the service to check (e.g., "HDFS", "YARN", "HBASE")

Returns: Detailed service information (success: comprehensive details, failure: English error message)

Starts all services in an Ambari cluster (equivalent to "Start All" in Ambari Web UI).

[Tool Role]: Dedicated tool for bulk starting all services in the cluster, automating mass startup.

[Core Functions]:

• Start all installed services simultaneously

• Return request information for progress tracking

• Provide clear success or error message for LLM automation

[Required Usage Scenarios]:

• When users request to "start all services", "start everything", "cluster startup"

• When recovering cluster after maintenance or outage

• When users mention mass startup, bulk start, or cluster bring-up

Returns: Start operation result (success: request info, failure: English error message)

Stops all services in an Ambari cluster (equivalent to "Stop All" in Ambari Web UI).

[Tool Role]: Dedicated tool for bulk stopping all services in the cluster, automating mass shutdown.

[Core Functions]:

• Stop all running services simultaneously

• Return request information for progress tracking

• Provide clear success or error message for LLM automation

[Required Usage Scenarios]:

• When users request to "stop all services", "stop everything", "cluster shutdown"

• When cluster maintenance or troubleshooting requires mass shutdown

• When users mention mass shutdown, bulk stop, or cluster halt

Returns: Stop operation result (success: request info, failure: English error message)

Starts a specific service in the Ambari cluster.

[Tool Role]: Dedicated tool for automated start of Ambari services, ensuring safe and monitored startup.

[Core Functions]:

• Start the specified service and initiate Ambari request

• Return request information for progress tracking

• Provide clear success or error message for LLM automation

[Required Usage Scenarios]:

• When users request to "start" a service (e.g., "start HDFS", "start YARN")

• When recovering stopped services

• When maintenance or configuration changes require a service start

• When users mention service start, bring up service, or automated start

Args: service_name: Name of the service to start (e.g., "HDFS", "YARN", "HBASE")

Returns: Start operation result (success: request info, failure: error message) - Success: Multi-line string with request ID, status, monitor URL, and instructions for progress tracking - Failure: English error message describing the problem

Stops a specific service in the Ambari cluster.

[Tool Role]: Dedicated tool for automated stop of Ambari services, ensuring safe and monitored shutdown.

[Core Functions]:

• Stop the specified service and initiate Ambari request

• Return request information for progress tracking

• Provide clear success or error message for LLM automation

[Required Usage Scenarios]:

• When users request to "stop" a service (e.g., "stop HDFS", "stop YARN")

• When maintenance or troubleshooting requires a service shutdown

• When users mention service stop, shutdown, or automated stop

Args: service_name: Name of the service to stop (e.g., "HDFS", "YARN", "HBASE")

Returns: Stop operation result (success: request info, failure: error message) - Success: Multi-line string with request ID, status, monitor URL, and instructions for progress tracking - Failure: English error message describing the problem

Retrieves the status and progress of a specific Ambari request operation.

[Tool Role]: Dedicated tool for real-time tracking and reporting of Ambari request status.

[Core Functions]:

• Query the status, progress, and context of a request by its ID

• Provide detailed status (PENDING, IN_PROGRESS, COMPLETED, FAILED, etc.)

• Show progress percentage and timing information

• Return actionable status for automation and LLM integration

[Required Usage Scenarios]:

• When users ask for the status or progress of a specific operation/request

• When monitoring or troubleshooting Ambari operations

• When tracking bulk or individual service actions

• When users mention request ID, operation status, or progress

Args: request_id: ID of the Ambari request to check (int)

Returns: Request status information (success: detailed status and progress, failure: error message) - Success: Multi-line string with request ID, status, progress, context, start/end time, and status description - Failure: English error message describing the problem

Restarts a specific service in an Ambari cluster (stop then start).

[Tool Role]: Dedicated tool for automated restart of Ambari services, ensuring safe stop and start sequence.

[Core Functions]:

• Stop the specified service and wait for completion

• Start the service and wait for completion

• Return clear success or error message for LLM automation

[Required Usage Scenarios]:

• When users request to "restart" a service (e.g., "restart HDFS", "restart YARN")

• When troubleshooting or recovering service issues

• When maintenance or configuration changes require a restart

• When users mention service restart, safe restart, or automated restart

Args: service_name: Name of the service to restart (e.g., "HDFS", "YARN")

Returns: Restart operation result (success: English completion message, failure: English error message) - Success: "Service '<service_name>' restart operation completed successfully." - Failure: "Error: ..." with details

Restarts all services in the Ambari cluster (stop all, then start all).

[Tool Role]: Dedicated tool for automated bulk restart of all Ambari services, ensuring safe stop and start sequence.

[Core Functions]:

• Stop all running services and wait for completion

• Start all services and wait for completion

• Return clear success or error message for LLM automation

[Required Usage Scenarios]:

• When users request to "restart all services", "bulk restart", "cluster-wide restart"

• When troubleshooting or recovering cluster-wide issues

• When maintenance or configuration changes require a full restart

Returns: Bulk restart operation result (success: English completion message, failure: English error message) - Success: "All services restart operation completed successfully." - Failure: "Error: ..." with details

Retrieves the list of hosts in the Ambari cluster.

[Tool Role]: Dedicated tool for listing all hosts registered in the Ambari cluster.

[Core Functions]:

• Query Ambari REST API for host list

• Return host names and API links

• Provide formatted output for LLM automation and cluster management

[Required Usage Scenarios]:

• When users request cluster host list or host details

• When auditing or monitoring cluster nodes

Returns: List of hosts (success: formatted list, failure: error message)

Retrieves detailed information for a specific host or all hosts in the Ambari cluster.

[Tool Role]: Dedicated tool for retrieving comprehensive host details including metrics, hardware info, and components.

[Core Functions]:

• If host_name provided: Query specific host information

• If host_name not provided: Query all hosts and their detailed information

• Return host hardware specs, state, metrics, and assigned components

• Provide formatted output for LLM automation and cluster management

[Required Usage Scenarios]:

• When users request specific host details or host status

• When users request all hosts details or cluster-wide host information

• When auditing or monitoring individual or all cluster nodes

• When troubleshooting host-specific issues

Args: host_name: Name of the specific host to retrieve details for (optional, e.g., "bigtop-hostname0.demo.local")

Returns: Detailed host information (success: formatted details, failure: error message)

List all users in the Ambari system.

Returns a formatted list of all users with their basic information.

Get detailed information about a specific user.

Args: user_name: The username to retrieve details for

Returns: Detailed user information including profile, permissions, and authentication sources

Retrieve current alerts or alert history from Ambari cluster.

[Tool Role]: Unified tool for retrieving both current/active alert status and historical alert events from Ambari cluster

[Core Functions]:

• Current mode: Retrieve current alerts for entire cluster, specific service, or specific host

• History mode: Retrieve alert history for entire cluster, specific service, or specific host

• Support filtering by alert state (CRITICAL, WARNING, OK, UNKNOWN)

• Support filtering by definition name

• Current mode: Support filtering by maintenance state (ON, OFF)

• History mode: Support filtering by time range with from_timestamp/to_timestamp

• Support different output formats (detailed, summary, compact, groupedSummary for current)

• History mode: Provide pagination support for large datasets

• Provide current time context for LLM natural language time calculations

[Required Usage Scenarios]:

• Current mode: When users request current alerts, active alerts, or alert status

• Current mode: When monitoring immediate cluster health

• Current mode: When investigating current issues or troubleshooting active problems

• History mode: When users request alert history, past alerts, or historical alert data

• History mode: When monitoring alert trends or analyzing alert patterns

• History mode: When investigating past alert incidents or troubleshooting

• When users mention alert status, current problems, cluster health, alert events, alert timeline, or alert logs

Args: mode: "current" for active alerts, "history" for past events (default: "current") cluster_name: Name of cluster (uses default if not specified) service_name: Filter by specific service name (e.g., HDFS, YARN) host_name: Filter by specific host name state_filter: Filter by alert state (CRITICAL, WARNING, OK, UNKNOWN) definition_name: Filter by alert definition name maintenance_state: Filter by maintenance state (ON, OFF) - current mode only from_timestamp: Start timestamp in milliseconds (Unix epoch) - history mode only to_timestamp: End timestamp in milliseconds (Unix epoch) - history mode only include_time_context: Add current time information for LLM natural language processing limit: Maximum number of alert entries to return page_size: Number of entries per page (default: 100) - history mode only start_page: Starting page number (default: 0) - history mode only format: Output format - 'detailed', 'summary', 'compact', or 'groupedSummary' (current mode only)

Returns: Alert information (success: formatted alerts, failure: English error message)

Retrieve current alerts from Ambari cluster.

DEPRECATED: This function is deprecated in favor of get_alerts_history with mode="current". This wrapper is maintained for backward compatibility.

Return the canonical English prompt template (optionally a specific section).

Simplified per project decision: only a single English template file PROMPT_TEMPLATE.md is maintained.

Args: section: (optional) section number or keyword (case-insensitive) e.g. "1", "purpose", "tool map". mode: (optional) if "headings" returns just the list of section headings with numeric indices.