Skip to main content
Glama

getStatus

Check Jenkins instance status and health information to monitor system availability and performance.

Instructions

Get Jenkins instance status and health information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the getStatus tool. It fetches overall load, queue, and nodes information from Jenkins APIs and returns formatted status data.
    export async function getStatus(client) {
    	try {
    		const [overallLoad, queue, nodes] = await Promise.all([
    			client.get("/overallLoad/api/json"),
    			client.get("/queue/api/json"),
    			client.get("/computer/api/json"),
    		]);
    
    		const status = {
    			queueLength: queue.data?.items?.length || 0,
    			totalExecutors: overallLoad.data?.totalExecutors || 0,
    			busyExecutors: overallLoad.data?.busyExecutors || 0,
    			availableExecutors: overallLoad.data?.availableExecutors || 0,
    			nodes:
    				nodes.data?.computer?.map((c) => ({
    					displayName: c.displayName,
    					offline: c.offline,
    					numExecutors: c.numExecutors,
    				})) || [],
    		};
    
    		return success("getStatus", { status });
    	} catch (error) {
    		return formatError(error, "get status");
    	}
    }
  • Tool registration in the central registry, defining name, description, empty input schema, and reference to the handler function.
    getStatus: {
    	name: "getStatus",
    	description: "Get Jenkins instance status and health information",
    	inputSchema: {
    		type: "object",
    		properties: {},
    	},
    	handler: getStatus,
    },
  • Input schema for getStatus tool, which requires no parameters.
    inputSchema: {
    	type: "object",
    	properties: {},
    },
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves status and health information, implying a read-only operation, but doesn't specify details like authentication requirements, rate limits, or what specific health metrics are included. This is a significant gap for a tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It is front-loaded and wastes no space, making it highly concise and well-structured for quick understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema) and lack of annotations, the description is minimally adequate. It covers the basic purpose but lacks details on behavioral aspects like return format or usage context, which could be helpful for an agent. It meets the minimum viable threshold without being fully informative.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so the schema fully documents that no inputs are required. The description doesn't need to add parameter details, and it appropriately doesn't mention any, earning a baseline score above 3 for correctly aligning with the schema's emptiness.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and the resource 'Jenkins instance status and health information', making the purpose specific and understandable. However, it doesn't explicitly differentiate this tool from siblings like 'whoAmI' or 'getQueueInfo', which might also provide status-related information, so it doesn't reach the highest score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, exclusions, or specific contexts for usage, such as checking system health before triggering builds. This leaves the agent with minimal direction on tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/umishra1504/Jenkins-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server