Skip to main content
Glama

GitPicker

get_issues

列出 GitHub 仓库当前打开的 Issue 或 PR(编号、标题、作者、标签、评论数)。当用户想了解仓库的问题反馈、开发讨论或待合并的 PR 时使用。匿名访问,私有仓库的 Issues 不在此列。

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

Input Schema

NameRequiredDescriptionDefault
kindNo要列 Issue 还是 PR,默认 issue
pageNo页码,从 1 开始,默认 1(每页 30 条)
repoYes仓库名
ownerYes仓库属主

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses anonymous/unauthenticated access, the private-repo exclusion, and that only currently open items are returned. It omits rate limits or failure behavior, but the essential access and scope traits are covered.

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 compact sentences: what it returns, when to use it, and the access constraint, in that order. The parenthetical field list is informative rather than filler. Slightly more could be trimmed, but nothing is redundant.

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?

For a 4-parameter read tool with no output schema, the description supplies return fields, scope, and access limitations, which is close to what an agent needs. The main residual gap is pagination behavior, though the schema covers page and page size.

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 100%, so the schema already documents kind, page, repo, and owner, including the default of 1 page / 30 items. The description adds the issue-vs-PR distinction implicitly but no format or semantics beyond what the schema states, making 3 the correct baseline.

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 opens with a concrete verb and resource: list currently open Issues or PRs in a GitHub repo, then enumerates the returned fields (number, title, author, labels, comment count). It clearly differs from get_commits, get_repo, and list_releases by resource. It stops short of naming a sibling it could be confused with, so it lands at 4 rather than 5.

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?

It gives an explicit trigger: use it when the user wants issue feedback, development discussion, or pending-merge PRs. It also states a boundary condition (anonymous access; private-repo Issues are not covered). No explicit 'use X instead' routing is present, which keeps it out of 5 territory.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources