Skip to main content
Glama
Sign In
omni-dev

omni-dev

by rust-works
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

jira_link_list

List inward and outward links on a JIRA issue, returning YAML with link type, direction, and linked issue key and summary.

Instructions

List inward and outward links on a JIRA issue. Returns YAML with one entry per link (id, link_type, direction, linked_issue_key, linked_issue_summary). Mirrors omni-dev atlassian jira link list.

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": {
      "key": "<key>"
    },
    "name": "jira_link_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesJIRA issue key (e.g., `PROJ-123`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.40.0
  2. Removedv0.39.0
  3. Changed2 schema fields changedv0.33.0
    • removedInput schema / description
      Removed value: -"Parameters for the `jira_link_list` tool."
    • removedInput schema / title
      Removed value: -"LinkListParams"
  4. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden of disclosing behavior. It explicitly states the return format (YAML with specific fields) and that both inward and outward links are included, which goes beyond a simple 'list links' description. It also references a CLI command for additional familiarity, but does not mention error handling or prerequisites.

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 concise sentences with no redundant information. The first sentence states the action, and the second provides output format and CLI reference. Every sentence adds value.

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

Completeness5/5

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

Given the simple one-parameter tool with no annotations and no output schema, the description is remarkably complete: it states what it does, the direction scope, and the exact YAML fields returned. This effectively serves as an implicit output schema, so the description is self-contained for most usage.

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?

The input schema fully describes the single `key` parameter with an example, and the description does not add any additional parameter-specific information. The schema coverage is 100%, so no compensation is needed; baseline of 3 applies.

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

Purpose5/5

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

The description uses the specific verb 'List' and identifies the resource 'inward and outward links on a JIRA issue', which clearly distinguishes it from sibling tools like jira_link_create, jira_link_remove, and jira_link_types. The scope 'inward and outward' adds precision.

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

Usage Guidelines4/5

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

The description clearly indicates this tool is for listing links on a JIRA issue, giving clear context for when to use it. However, it does not explicitly mention alternatives or when-not-to-use, though the name and sibling set (e.g., jira_link_create, jira_link_remove) imply those are for other operations.

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