@znmin/jenkins-mcp-server

by znmin

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

set_node_config

Updates a Jenkins node's configuration by applying the provided XML config to the named node.

Instructions

Set specific node config in Jenkins.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "config_xml": "<config_xml>"
    },
    "name": "set_node_config"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`config_xml`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 14, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations indicate a write operation (readOnlyHint=false), and the description confirms mutation with 'set'. However, no details about side effects, required permissions, error outcomes, or config replacement behavior are disclosed.

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

Conciseness3/5

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

The description is extremely concise at 6 words, which is appropriate for a simple tool but lacks necessary detail. It is front-loaded but too sparse.

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

Completeness2/5

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

With no output schema and minimal annotations, the description should cover effect, return values, and error handling. It fails to do so, leaving gaps for a 2-parameter write operation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain parameters. It only names 'name' and 'config_xml' without clarifying their types, formats, or constraints (e.g., what XML schema is expected).

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 action ('set') and the resource ('node config in Jenkins'), distinguishing it from sibling tools like get_node_config and set_item_config. However, it lacks specificity about the config scope (e.g., global vs. per-node).

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?

No guidance on when to use this tool versus alternatives (e.g., set_item_config). No prerequisites or context provided, leaving the agent with no decision support.

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