Query items from Jenkins
Query items from Jenkins
Args: class_pattern: The pattern of the _class fullname_pattern: The pattern of the fullname color_pattern: The pattern of the color folder_depth: The maximum depth of folders to traverse. If None, traverses all levels.
Returns: A list of items
| Name | Required | Description | Default |
|---|---|---|---|
| folder_depth | No | ||
| class_pattern | No | ||
| color_pattern | No | ||
| fullname_pattern | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v3.6.0Input schema / properties / class_pattern / anyOfAdded value: +[
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / class_pattern / typeRemoved value: -"string"Input schema / properties / color_pattern / anyOfAdded value: +[
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / color_pattern / typeRemoved value: -"string"Input schema / properties / fullname_pattern / anyOfAdded value: +[
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / fullname_pattern / typeRemoved value: -"string"v3.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It says nothing about whether this is a read-only operation, auth requirements, result size/pagination, or the folder-traversal cost implied by 'traverses all levels'. The only behavioral hint is the folder_depth traversal note.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The docstring is appropriately sized, front-loads the purpose, then lists args and the return in a scannable structure. Slightly boilerplate 'Returns: A list of items' that adds little given an output schema exists.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, return values needn't be explained, and the params are covered. But for an unannotated query tool with 4 optional filtering params, the missing pattern-syntax semantics and absence of any usage/behavioral context leave meaningful gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate, and it does document all four parameters including the None=all-levels semantics of folder_depth. However, it does not specify what pattern syntax the *_pattern args expect (regex, glob, substring), leaving a real ambiguity for a query tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource (query items from Jenkins) with an implied filtering purpose via the *_pattern args. It does not, however, distinguish itself from sibling tools like get_all_items or get_item, so an agent must infer the difference itself.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus get_all_items, get_item, or other retrieval siblings, and no stated prerequisites or exclusions. The agent is left to guess from the argument names alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.