jenkins-http-mcp-server

jenkins_get_json

Read-only

Fetch Jenkins JSON API data using a relative path, while rejecting external URLs and traversal to ensure secure access.

Instructions

GET a relative Jenkins JSON API path. Rejects external URLs and traversal.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	Yes
`query`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv2.0.0Sep 6, 2026

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / description

Added value: +"Structured content returned by successful Jenkins tools."

addedOutput schema / properties

Added value: +{
+  "data": {
+    "title": "Data"
+  },
+  "ok": {
+    "const": true,
+    "title": "Ok",
+    "type": "boolean"
+  }
+}

addedOutput schema / required
```
Added value: +[
+  "ok",
+  "data"
+]
```

changedOutput schema / title

Previous value: -"jenkins_get_jsonDictOutput"New value: +"ToolSuccess"

First observedv0.1.0May 6, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already mark the tool as read-only; the description adds useful behavioral context by stating it rejects external URLs and path traversal. No contradiction and no hidden write or destructive behavior is implied.

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?

One sentence front-loads the verb and resource and then states the key constraint. There is no filler or redundant restatement of the tool name.

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

Completeness3/5

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

The description is adequate for the simple 'path' parameter, and the output schema covers return values, but it lacks guidance on the 'query' parameter and on choosing this tool over specialized siblings. For a generic Jenkins JSON API accessor, this is a minimal but not fully complete definition.

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%, and the description only clarifies 'path' as a relative Jenkins API path. The optional 'query' parameter is left entirely undocumented by both schema and description, so an agent must guess at its formatting and purpose.

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 states a specific verb ('GET'), resource ('relative Jenkins JSON API path'), and constraints ('rejects external URLs and traversal'). It is distinct from the specialized sibling tools that target specific Jenkins objects, though it does not explicitly name an alternative.

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 given about when to use this generic API-path tool versus the many specialized siblings. The security restriction is a validity constraint, not a usage condition, and no fallback or alternative condition is mentioned.

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

Deploy Server