Server Configuration
Describes the environment variables required to run the server.
Name | Required | Description | Default |
---|---|---|---|
PORT | No | The port number for HTTP server when in HTTP transport mode | 18000 |
AMBARI_HOST | Yes | The hostname or IP address of the Ambari server | |
AMBARI_PASS | Yes | The password for authenticating with Ambari | |
AMBARI_PORT | Yes | The port number of the Ambari server | |
AMBARI_USER | Yes | The username for authenticating with Ambari | |
FASTMCP_PORT | No | When set, enables HTTP transport mode instead of stdio mode | |
AMBARI_LOG_LEVEL | No | The logging level for the application | INFO |
AMBARI_CLUSTER_NAME | Yes | The name of the Ambari cluster to manage |
Schema
Prompts
Interactive templates invoked by user choice
Name | Description |
---|---|
prompt_template_full | Return the full canonical prompt template. |
prompt_template_headings | Return compact list of section headings. |
prompt_template_section | Return a specific prompt template section by number or keyword. If 'section' is omitted: returns a concise help block plus a compact headings list instead of erroring. |
Resources
Contextual data attached and managed by the client
Name | Description |
---|---|
No resources |
Tools
Functions exposed to the LLM to take actions
Name | Description |
---|---|
dump_configurations | Unified configuration introspection tool (supersedes get_configurations & list_configurations & dump_all_configurations). Modes:
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 |
get_cluster_info | 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]:
[Required Usage Scenarios]:
Returns: Cluster basic information (success: formatted info, failure: English error message) |
get_active_requests | 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]:
[Required Usage Scenarios]:
Returns: Active requests information (success: active request list, failure: error message) |
get_cluster_services | 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]:
[Required Usage Scenarios]:
[Absolutely Prohibited Scenarios]:
Returns: Cluster service list with status information (success: service list with status, failure: error message) |
get_service_status | 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]:
[Required Usage Scenarios]:
Args: service_name: Name of the service to check (e.g., "HDFS", "YARN", "HBASE") Returns: Service status information (success: detailed status, failure: error message) |
get_service_components | 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]:
[Required Usage Scenarios]:
Args: service_name: Name of the service (e.g., "HDFS", "YARN", "HBASE") Returns: Service components detailed information (success: formatted list, failure: English error message) |
get_service_details | 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]:
[Required Usage Scenarios]:
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) |
start_all_services | 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]:
[Required Usage Scenarios]:
Returns: Start operation result (success: request info, failure: English error message) |
stop_all_services | 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]:
[Required Usage Scenarios]:
Returns: Stop operation result (success: request info, failure: English error message) |
start_service | 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]:
[Required Usage Scenarios]:
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 |
stop_service | 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]:
[Required Usage Scenarios]:
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 |
get_request_status | 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]:
[Required Usage Scenarios]:
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 |
restart_service | 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]:
[Required Usage Scenarios]:
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 |
restart_all_services | 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]:
[Required Usage Scenarios]:
Returns: Bulk restart operation result (success: English completion message, failure: English error message) - Success: "All services restart operation completed successfully." - Failure: "Error: ..." with details |
list_hosts | Retrieves the list of hosts in the Ambari cluster. [Tool Role]: Dedicated tool for listing all hosts registered in the Ambari cluster. [Core Functions]:
[Required Usage Scenarios]:
Returns: List of hosts (success: formatted list, failure: error message) |
get_host_details | 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]:
[Required Usage Scenarios]:
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_users | List all users in the Ambari system. Returns a formatted list of all users with their basic information. |
get_user | 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 |
get_alerts_history | 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]:
[Required Usage Scenarios]:
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) |
get_current_alerts | 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. |
get_prompt_template | Return the canonical English prompt template (optionally a specific section). Simplified per project decision: only a single English template file 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. |