Skip to main content
Glama
Murtaza1211

mcp-server

by Murtaza1211
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
read_configA

SSH to a server and read a Liberty-style app's server.xml plus jvm.options, server.env, bootstrap.properties, and any *.properties files referenced from server.xml, with password/token/secret/key values redacted.

Args:
    server_ip: Hostname or IP address of the server to connect to over SSH.
    os_user: SSH username to authenticate as.
    ssh_key: Path to the private key file (on this machine) used for authentication.
    deployment_directory: Base deployment directory containing the application folder.
    application: Name of the application subfolder to read config from.
health_checkA

SSH to a server and check an IBM Liberty app's health: an HTTP probe against http://127.0.0.1:port/uri (via curl/wget/python3, whichever is present), and a process check via ps -ef (no JDK/jps/server-status dependency, no root paths).

Args:
    server_ip: Hostname or IP address of the server to connect to over SSH.
    os_user: SSH username to authenticate as.
    ssh_key: Path to the private key file (on this machine) used for authentication.
    port: Local port the application listens on.
    uri: URI path to request for the HTTP health check (e.g. /health).
    application: Application/server name to look for among running processes.
list_logsA

SSH to a server and enumerate every file under //logs/ (Liberty's own messages.log/console.log/trace.log/ffdc/*, plus any app-written logs in subdirectories), with size, last-modified time, and a rough category for each. Call this first, then pass the relevant paths as log_files to analyze_logs - avoids blindly grepping every file (trace.log especially can be huge).

Args:
    server_ip: Hostname or IP address of the server to connect to over SSH.
    os_user: SSH username to authenticate as.
    ssh_key: Path to the private key file (on this machine) used for authentication.
    deployment_directory: Base deployment directory containing the application folder.
    application: Name of the application subfolder whose logs/ directory to list.
analyze_logsA

SSH to a server and search the app's logs for the given strings/exception names, returning matches with a couple of lines of context. Time filtering is best-effort: Liberty log entries carry a leading timestamp but continuation/stack-trace lines don't repeat it, so a match is only excluded when a timestamp was actually found and falls outside the window - anything unparseable is kept rather than silently dropped.

If log_files is omitted, every discovered log file is searched, except ones over ~25MB
(skipped and reported back) - call list_logs first and pass specific log_files to search
those anyway, or to scope the search down for a large deployment.

Args:
    server_ip: Hostname or IP address of the server to connect to over SSH.
    os_user: SSH username to authenticate as.
    ssh_key: Path to the private key file (on this machine) used for authentication.
    deployment_directory: Base deployment directory containing the application folder.
    application: Name of the application subfolder whose logs/ directory to search.
    search: Strings or exception names to search for (case-insensitive, literal match).
    start_time: Optional ISO-8601 timestamp; matches before this are excluded when detectable.
    end_time: Optional ISO-8601 timestamp; matches after this are excluded when detectable.
    log_files: Optional list of paths (relative to logs/, as returned by list_logs) to
        restrict the search to. Recommended for large deployments or to include files
        skipped by the size cap.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: read_config reads configuration files, health_check performs health checks, list_logs enumerates log files, and analyze_logs searches logs. There is no overlap or ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (read_config, health_check, list_logs, analyze_logs), making them predictable and easy to understand.

Tool Count4/5

With 4 tools, the set is reasonably scoped for a diagnostics-focused server. It covers key operations (config reading, health check, log listing, log searching) without being overly numerous or too sparse.

Completeness3/5

The tool surface covers diagnostics well but lacks lifecycle operations such as deploy, start, stop, or config editing. This is a notable gap for managing Liberty applications, though the set is complete for the implied diagnostic purpose.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources