Gyuniverse GitHub Projects MCP

list_github_projects

Read-onlyIdempotent

Fetches GitHub Projects v2 accessible to the authenticated user within an owner allowlist. Use it to review available projects before reading or updating them.

Instructions

List GitHub Projects v2 visible to the authenticated principal within the server owner/Project allowlists.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 12, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered structurally. The description adds the allowlist/principal-scoping constraint, which is genuine behavioral context, but says nothing about pagination behavior, access failures for non-allowlisted owners, or result shape.

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 front-loaded sentence with no filler; the scope qualifier follows the core verb+resource immediately.

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?

With 0% parameter description coverage, no output schema, and a dense sibling ecosystem, the definition omits owner format, pagination semantics, and return shape. For a list tool in this context it is under-specified beyond the surface purpose.

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%, so the description carries the burden but adds none: it never explains that 'owner' is a user/org login identifier nor that 'first' is a page-size cap (default 20, max 100). The one clause about allowlists loosely constrains the owner parameter but not clearly enough to compensate.

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?

States a specific verb ('List'), resource ('GitHub Projects v2'), and visibility scope ('visible to the authenticated principal within the server owner/Project allowlists'). This distinguishes it from siblings such as list_github_project_items and list_github_project_fields, though it never names those siblings explicitly.

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 get_github_project (single project) or the list_github_project_items/list_github_project_fields siblings. The allowlist mention hints at scope but gives no when/when-not or alternative-routing instructions.

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

Deploy Server