Skip to main content
Glama

add_issue_relationship

Creates a relationship between two issues, such as related-to, duplicate-of, parent-of, child-of, or has-duplicate, to link dependencies and track duplicates.

Instructions

Creates a relationship between two issues (e.g. related-to, duplicate-of, parent-of, child-of, has-duplicate).

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": {
      "issue_id": "<issue_id>",
      "target_issue_id": "<target_issue_id>"
    },
    "name": "add_issue_relationship"
  }
}

Input Schema

NameRequiredDescriptionDefault
issue_idYes
target_issue_idYes
relationship_typeNorelated-to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing: it does not say whether the operation is idempotent, what happens if the relationship already exists or is invalid, whether the relationship is directional, or whether permissions are required. Only the bare fact of creation is conveyed.

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?

A single well-formed sentence with the purpose front-loaded and no filler. The parenthetical list is somewhat redundant with the schema enum, costing a point on economy but not on clarity.

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

Completeness2/5

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

For a mutation tool with no annotations, no output schema, and zero schema description coverage, the description is too thin — it omits direction semantics, duplicate handling, error conditions, and the return value. An agent could invoke it but could easily create an inverted or unexpected relationship.

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 description coverage is 0% across three parameters, and the description only restates the enum values already present in the schema rather than adding meaning. Critically, it does not explain the directionality of issue_id versus target_issue_id, which materially changes what 'parent-of' or 'duplicate-of' means — a real semantic gap, though the example types do at least anchor the relationship_type parameter.

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 gives a specific verb plus resource ('Creates a relationship between two issues') and enumerates the relationship kinds, so the agent knows exactly what the tool does. It stops short of distinguishing itself from the sibling delete_issue_relationship or explaining scope, but the core purpose is unambiguous.

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?

There is no guidance on when to use this versus alternatives (e.g. delete_issue_relationship for removal, or attaching tags/notes for other associations), nor any prerequisites such as required permissions or whether the two issues must be in the same project. The agent must infer all selection criteria.

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