Skip to main content
Glama

set_node_config

Sets a Jenkins node's configuration by applying an XML definition. Update node settings directly without manual UI steps.

Instructions

Set specific node config in Jenkins

Args: name: The name of the node config_xml: The config XML of the node

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
config_xmlYes

Implementation Reference

  • The MCP tool handler for 'set_node_config'. It is decorated with @mcp.tool(tags=['write']), accepts a context, node name, and config XML string, and delegates to the REST client.
    @mcp.tool(tags=['write'])
    async def set_node_config(ctx: Context, name: str, config_xml: str) -> None:
        """Set specific node config in Jenkins
    
        Args:
            name: The name of the node
            config_xml: The config XML of the node
        """
        jenkins(ctx).set_node_config(name=name, config_xml=config_xml)
  • The Jenkins REST client method that sends a POST request to the node config endpoint with the XML data.
    def set_node_config(self, *, name: str, config_xml: str) -> None:
        """Set the configuration for a node.
    
        Args:
            name: The name of the node.
            config_xml: The node configuration as an XML string.
        """
        self.request(
            'POST',
            rest_endpoint.NODE_CONFIG(name=name),
            headers=self.DEFAULT_HEADERS,
            data=config_xml,
        )
  • The REST endpoint definition for node config operations (GET/POST to computer/{name}/config.xml).
    NODE_CONFIG = RestEndpoint('computer/{name}/config.xml')
  • The @mcp.tool() decorator registers this function as an MCP tool named 'set_node_config' with a 'write' tag.
    @mcp.tool(tags=['write'])
    async def set_node_config(ctx: Context, name: str, config_xml: str) -> None:
        """Set specific node config in Jenkins
    
        Args:
            name: The name of the node
            config_xml: The config XML of the node
        """
        jenkins(ctx).set_node_config(name=name, config_xml=config_xml)
Behavior2/5

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

No annotations exist, so description carries full burden. It indicates mutation ('set') but lacks details on permissions, idempotency, error behavior, or what happens if the node does not exist.

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

Conciseness4/5

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

Description is short and to the point with no wasted words. The argument list is presented clearly, though a more structured format (e.g., bullet points) could improve readability.

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?

Given no output schema, no annotations, and moderate complexity, the description is too minimal. It omits return values, error handling, and does not reference related siblings like get_node_config.

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 has 0% description coverage. The description adds basic labels ('name' and 'config_xml') but no details on format, constraints, or expected XML structure, failing to compensate for poor schema.

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 resource (node config) in Jenkins. It distinguishes from the sibling get_node_config by implying a write operation, but does not explicitly differentiate.

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 like get_node_config. No prerequisites, context, or conditions for use are provided.

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/lanbaoshen/mcp-jenkins'

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