Skip to main content
Glama
Sign In
CNB Remote MCP

CNB Remote MCP

by htazq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List issues

issue_list
Read-onlyIdempotent

List repository issues with optional filters for state, author, labels, keyword, and pagination to find and review relevant work items.

Instructions

List issues of a repository with optional filters.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1
repoYesRepository path, e.g. "owner/repo" or "group/subgroup/repo"
stateNoFilter by state
authorNoFilter by author username
labelsNoComma-separated label names
keywordNoSearch keyword in title/body
page_sizeNoItems per page (max 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/5.0
Behavior2/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 fully covered. The description adds nothing beyond that: it does not say what the default state filter returns (open vs. all), how pagination terminates, or whether results are sorted in any particular way.

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 wasted words. It is arguably too terse for a seven-parameter tool, but nothing is redundant or buried.

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

Completeness3/5

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

For a simple filtered-list tool with full schema coverage and strong annotations, the essentials are covered. The remaining gaps are the ambiguous defaults (state filtering, page_size default, pagination) that an agent would need in order to call it predictably on the first try.

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 every parameter including repo format, state enum, label comma-separated syntax and page_size cap is already documented in the schema. The description adds no meaning beyond that, which is the baseline expectation when the schema does all the work.

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 gives a specific verb and resource ("List issues of a repository") plus a scope note ("with optional filters"), so an agent knows exactly what it retrieves. It does not, however, distinguish this from siblings like issue_get or pr_list, which the agent must infer.

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?

No when-to-use guidance is offered: no exclusion of issue_get for a single issue, no mention of when to use keyword/labels vs. repo_search, and no note on default behavior for the state filter. The phrase "optional filters" only hints at usage rather than directing it.

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