Jenkins MCP Server

Overview Schema Source Related Servers Discussions Admin

Get Known Issue

get_known_issue

Read-onlyIdempotent

Retrieve the full knowledge base entry for a known issue by ID, including symptoms, root cause, fix, and investigation notes to support triage and reuse solved team knowledge.

Instructions

Full text of one knowledge base entry: scope, symptoms, root cause, fix, how it was found, red herrings. Content is written by the team (reviewed) - drafts are marked as unreviewed.

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": {
      "id": "<id>"
    },
    "name": "get_known_issue"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Entry id like KB-0001 (drafts too)

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 1, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely new context: the entry is team-written and reviewed, and drafts are flagged as unreviewed, which tells the agent how much to trust the content. It stops short of stating error behavior for missing ids or whether drafts are returned by default.

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?

Two short sentences, front-loaded with what the tool returns and followed by the trust/review caveat. Dense and waste-free, though the fragment-style field list is slightly terse.

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?

An output schema exists, so return structure need not be described, and the description covers the content shape plus the reviewed/unreviewed nuance. For a single-parameter read tool this is close to sufficient; only error handling for invalid ids is unaddressed.

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

Parameters3/5

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

Schema coverage is 100% and the id format (KB-0001) is already documented in the schema. The description's only added signal is 'drafts too', which restates what the schema says. Baseline 3 is appropriate when the schema does the work.

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 precisely that it returns the full text of a single knowledge base entry and enumerates the fields it contains (scope, symptoms, root cause, fix, discovery, red herrings). The singular 'one entry' implicitly contrasts with the list/find siblings, but no sibling is named, so the differentiation is left to inference.

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 only implied: 'one knowledge base entry' plus the required id parameter suggests 'use when you already have an entry id'. There is no explicit statement of when to prefer this over find_known_issues or list_known_issues, and no guidance on what to do if the id is unknown.

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