Gyuniverse GitHub Projects MCP

get_github_project_item_relationships

Read-onlyIdempotent

Retrieve parent, sub-issue, blocks, and blocked-by relationships for an authorized Project Issue, returning only same-Project allowed-owner details; withheld counts and bounded coverage are explicit.

Instructions

Read native parent, sub-issue, blocks and blocked-by relationships for a GitHub Issue item in an authorized Project. Only same-Project, allowed-owner target details are returned; withheld counts and bounded coverage are explicit. Does not mutate GitHub or change get_blockers semantics.

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": {
      "owner": "<owner>",
      "number": "<number>",
      "itemId": "<itemId>"
    },
    "name": "get_github_project_item_relationships"
  }
}

Input Schema

Name	Required	Description	Default
`first`	No
`owner`	Yes
`itemId`	Yes
`number`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 12, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real value beyond that: only same-Project, allowed-owner target details are returned, and partial results are surfaced via withheld counts and bounded coverage. With no output schema, this visibility into filtering and truncation behavior is genuinely useful.

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?

Three tight sentences, front-loaded with the core purpose followed by return-scope caveats and a boundary disclaimer. Dense but every clause carries signal; only 'bounded coverage are explicit' borders on opaque phrasing.

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?

For a read-only tool with strong annotations and no output schema, the description covers scope and filtering reasonably well. It is incomplete on the undocumented parameter set, which an agent needs in order to call it correctly with owner/number/itemId.

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 there are four parameters (owner, number, itemId, first) that the description never explains. It does not say what itemId vs number mean, nor that 'first' is a page-size bound with a default of 50 and max of 100, so the description fails to compensate for the coverage gap.

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?

States a specific verb (Read) and a specific resource (native parent, sub-issue, blocks and blocked-by relationships for a GitHub Issue item in a Project). The closing clause explicitly distinguishes it from a close sibling, get_blockers, which most agents would otherwise confuse it with.

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 implied by the stated scope (fetching relationships for one item), and a negative boundary is given ('does not mutate GitHub'). However, there is no explicit when-to-use guidance versus alternatives such as get_blockers or the add/remove relationship tools, so the agent must infer the routing from the purpose sentence.

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

Deploy Server