Skip to main content
Glama

Upstream.codes

Search issues

search_issues
Read-only

Search one repository's issues and Change Requests. Supports qualifiers such as is:open, is:closed, is:issue, is:pr (Change Requests), is:merged, label:bug and author:handle. To list without a search term use list_issues or list_change_requests.

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
repoYesRepository slug.
ownerYesNamespace that owns the repository (user or organization handle).
queryYesSearch text and qualifiers; the repository is added for you.
cursorNonextCursor from a previous page.
perPageNoResults per page (default 30).

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the corpus spans both issues and Change Requests (is:pr) and that the repository filter is applied automatically, but says nothing about result ordering, match behavior, or how pagination interacts with search. Useful but thin on behavior beyond annotations.

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?

Two sentences, zero waste. Capability and scope come first, the qualifier examples second, and the routing rule last, so the reader hits the most decision-relevant information first.

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?

With no output schema, the description should reassure about result shape; it does not, though pagination params in the schema partly compensate. For a search tool with fully documented params and read-only annotations, the qualifier list and sibling routing make the definition sufficient to call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description goes beyond it by supplying the qualifier vocabulary for `query` — is:open, is:closed, is:issue, is:pr, is:merged, label:bug, author:handle — which the schema does not enumerate. That is real added meaning for the most important parameter.

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?

States a specific verb (search) and resource (issues and Change Requests) with explicit scope: 'one repository's issues'. The scoping detail both qualifies the tool and separates it from repo-wide or code search, so an agent can identify it 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit condition-selects-alternative rule: 'To list without a search term use list_issues or list_change_requests.' The when-not case is named along with the sibling that covers it, leaving nothing to inference about search vs. enumeration.

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