Gyuniverse GitHub Projects MCP

assign_work_item

Idempotent

Assign a GitHub user to an issue or pull request from a Project item. Resolves login, skips existing assignees, verifies the assignment, and returns audit metadata.

Instructions

Assign a GitHub user to the Issue or Pull Request represented by one authorized Project item. Admin/PM only in the current policy. Resolves the login, skips an already-assigned user, verifies the assignment, and returns actor-aware audit metadata.

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

Input Schema

Name	Required	Description	Default
`owner`	Yes
`itemId`	Yes
`number`	Yes
`assigneeLogin`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 12, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, readOnlyHint=false and openWorldHint=true, so safety is partly covered. The description still adds real behavior the annotations do not: login resolution, skipping an already-assigned user, post-assignment verification, and actor-aware audit metadata in the response.

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 action and permissions before the behavioral sequence. Dense but each sentence carries distinct information; no filler.

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

Completeness4/5

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

No output schema exists, and the description does cover the return shape (actor-aware audit metadata), the auth requirement, the mutation semantics, and the skip-and-verify sequence. The remaining gap is parameter meaning, which is left entirely to an undocumented schema.

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 all four required parameters, so the description must compensate and largely does not. Only 'Resolves the login' loosely maps to assigneeLogin, and 'authorized Project item' loosely hints at itemId; owner and number are never explained.

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 names a specific verb (Assign) and resource (a GitHub user to the Issue/PR behind a Project item), which is materially distinct from siblings like update_github_project_item_status or update_github_project_item_field. An agent can route here without opening the schema.

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?

'Admin/PM only in the current policy' gives an explicit authorization gate for when this tool is usable. It stops short of naming which alternative to use when the user is not authorized or when the item is not yet a project item, so it is clear context without explicit alternatives.

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

Deploy Server