Skip to main content
Glama
Sign In
@znmin/jenkins-mcp-server

@znmin/jenkins-mcp-server

by znmin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

query_items

Read-only

Query Jenkins items by class, color, and full name patterns to filter jobs and related objects for inspection.

Instructions

Query items from Jenkins.

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": "query_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
class_patternNo
color_patternNo
fullname_patternNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

The annotations already indicate readOnlyHint=true, so the tool is read-only. However, the description adds no further behavioral details, such as whether it returns a list, how patterns are matched, or any limitations.

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

Conciseness2/5

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

Although the description is short (one sentence), it is underspecified rather than concise. It lacks structure and fails to provide meaningful information beyond the tool's name.

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

Completeness1/5

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

Given the tool has 3 optional parameters, no output schema, and many sibling tools, the description is grossly incomplete. It does not clarify what items are queried, how patterns work, or when this tool is appropriate.

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 schema has zero description coverage for its three parameters (class_pattern, fullname_pattern, color_pattern). The description does not compensate by explaining their meaning, format (e.g., glob, regex), or examples. This leaves agents without essential usage information.

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

Purpose2/5

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

The description 'Query items from Jenkins' is vague; it does not specify what 'items' refers to (jobs, views, etc.) and does not distinguish itself from siblings like get_all_items or get_item. The schema parameters hint at filtering by patterns, but the description lacks specifics.

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 is provided on when to use this tool versus alternatives such as get_all_items or get_item. There is no mention of context, prerequisites, or exclusions.

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

Deploy Server

Other Tools