MCP Jenkins

Get Plugins With Problems

get_plugins_with_problems

Retrieve Jenkins plugins with missing dependencies, incompatible versions, core version mismatches, or configuration issues to diagnose and resolve plugin problems.

Instructions

Get all plugins with problems from Jenkins

These are plugins that have issues such as missing dependencies, incompatible versions, core version mismatch, or other configuration problems.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_plugins_with_problems"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.6.0+microtech.5Nov 7, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden, and it does partially by defining the filter criteria that determine what is returned. It does not state that the call is a read-only, side-effect-free operation, nor anything about cost, caching, or pagination — though a zero-argument 'Get' is low risk and an output schema exists to describe the response shape.

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?

Two short sentences, front-loaded with the action and resource, and the second sentence is entirely load-bearing because it defines the ambiguous word 'problems'. Nothing is redundant.

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

Completeness4/5

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

For a parameterless read tool with an output schema already documenting return values, the description supplies the one thing the schema cannot: the inclusion criteria for 'problems'. A brief note on whether the call is read-only or how heavy it is on a large controller would be the only remaining gap.

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 tool takes zero parameters, so there is no parameter meaning for the description to add; the baseline of 4 applies. Schema coverage is moot here since the object has no properties.

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?

States a specific verb and resource ('Get all plugins with problems from Jenkins') and then enumerates the failure modes counted as problems (missing dependencies, incompatible versions, core version mismatch, configuration problems). This implicitly separates it from siblings like get_plugins_with_updates and get_all_plugins, though it never names those alternatives explicitly.

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

Usage Guidelines3/5

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

Usage is implied: an agent would call this when diagnosing a broken Jenkins plugin setup rather than listing all plugins. There is no explicit when-to-use or when-not-to-use statement, and no pointer to get_all_plugins, get_plugin, or get_plugins_with_updates as the alternative for healthy or update-only listings.

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