@znmin/jenkins-mcp-server

Overview Schema Source Related Servers Discussions Admin

get_item_config

Read-only

Retrieves the configuration of a specific Jenkins item by full name, so you can inspect job or pipeline settings before making changes.

Instructions

Get specific item config from 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": {
      "fullname": "<fullname>"
    },
    "name": "get_item_config"
  }
}

Input Schema

Name	Required	Description	Default
`fullname`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 14, 2026

TDQS

C2.4/5.0

Behavior2/5

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

The annotation 'readOnlyHint: true' already indicates a safe read operation. The description adds no additional behavioral context (e.g., what happens if the item does not exist, or whether full configuration is returned). Minimal value beyond the annotation.

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 a single sentence, which is concise. However, it is too brief and omits critical details, sacrificing completeness for brevity.

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 one undocumented parameter, no output schema, and no explanation of the config format, the description is insufficient for reliable tool selection and usage. The agent may fail due to missing parameter semantics.

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

Parameters1/5

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

The single required parameter 'fullname' has 0% schema description coverage and is not explained in the tool description. The agent has no information about its format (e.g., full path, job name) or expected syntax, making invocation error-prone.

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', the resource 'item config', and the source 'Jenkins'. It is specific enough to distinguish from siblings like 'get_item' (which likely returns item details) and 'get_all_items' (list all).

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. The description does not mention prerequisites or conditions, leaving the agent to infer context from the name alone.

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