Skip to main content
Glama
Sign In
github-triage-mcp

github-triage-mcp

by kenzoob
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Search issues

search_issues

Search an allowlisted GitHub repository for issues matching a query to support AI triage and summarization.

Instructions

Searches issues in an allowlisted repository matching a query.

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

Input Schema

NameRequiredDescriptionDefault
repoYes
ownerYes
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it gives almost nothing. It hints at a scoping constraint ('allowlisted repository') but omits pagination, result caps, sorting, auth requirements, and whether the query uses GitHub search syntax or free text.

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?

A single front-loaded sentence with no filler. It is efficient, though the tightness comes at the cost of specificity rather than being paired with adequate detail.

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 three-parameter, all-required search tool with no annotations, no output schema, and no parameter documentation, this is too thin. The undefined query syntax and the owner/repo relationship leave real gaps an agent would hit at call time.

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 must compensate, and it does not. It gestures at 'repository' and 'query' but never explains the owner/repo split, the query syntax or operators, or the length and character constraints enforced by the schema.

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 ('Searches') and resource ('issues') with a scoping constraint ('in an allowlisted repository matching a query'). It is clear what the tool does, but it does not differentiate itself from the sibling search-like tools list_issues or get_issue, so an agent must infer the distinction.

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 when-to-use guidance and no mention of alternatives such as list_issues or get_issue. 'Matching a query' only weakly implies the search use case; nothing tells the agent when this is preferred over listing all issues.

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

Deploy Server

Other Tools