Gyuniverse GitHub Projects MCP

get_unassigned_work

Read-onlyIdempotent

Finds non-completed GitHub Project items lacking repository or Project assignee evidence, helping you identify and assign unowned tasks.

Instructions

Return non-completed Project items with no repository or Project assignee evidence.

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>"
    },
    "name": "get_unassigned_work"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 12, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds the meaningful scoping rule (excludes completed items and anything with assignee evidence), but says nothing about pagination, result size, or what 'evidence' means operationally.

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?

A single tight sentence, front-loaded with the return scope and no filler. Every word carries meaning.

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 4-parameter tool with no output schema and no parameter documentation, the description leaves required inputs (owner, number) and the includeArchived/pagination behavior unexplained. It defines the result set but not how to invoke it correctly.

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% across 4 parameters. The description explains none of them: owner, number, first (pagination cap), and includeArchived are left entirely to type/default inference, so it 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.

Purpose4/5

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

Names a specific retrieval action and its exact filter: non-completed Project items lacking repository or Project assignee evidence. This distinguishes it from get_my_work, get_backlog, and list_github_project_items, though it never explicitly says so.

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?

The filter semantics imply the use case (find orphaned/unassigned work), but there is no explicit when-to-use statement or named alternative among the many sibling list/get tools. Usage must be inferred from the filter definition.

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

Deploy Server