Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

github_issue_list

Read-only

Lists GitHub issues in the current repository via the gh CLI, helping you review open work items and track progress. Requires GitHub CLI authentication.

Instructions

List GitHub issues in the current repository using gh CLI (requires gh auth).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "github_issue_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1..40

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The one genuinely additive fact is the gh-auth dependency, but nothing is said about ordering, pagination, default page size behavior, or whether the list is truncated by the limit parameter — for an open-world network call that leaves gaps. Also, the repository scope is implied but not stated as an assumption (no repo argument exists).

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 zero filler: action, resource, scope, mechanism, and prerequisite in order of importance. Nothing to trim.

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 one-parameter read-only list tool this is close to sufficient — scope, mechanism, and auth are covered. Missing is any hint of what a result contains or how the limit interacts with the underlying gh CLI output (e.g., pagination), which matters because there is no output schema to fall back on.

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?

Only one parameter exists and the schema fully documents it (integer, default 15, description "1..40"), so schema coverage is 100%. The description adds no limit semantics, but the baseline for a single fully-documented parameter is high.

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") and resource ("GitHub issues") scoped to "the current repository", which separates it from github_pr_list by noun rather than by explicit contrast. Clear enough that an agent knows exactly what it retrieves, though it never names a sibling to differentiate against.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The parenthetical "(requires gh auth)" gives a real invocation prerequisite, which is useful. However, there is no statement of when to reach for this versus related tools (github_pr_list, checkpoint_list, audit_recent all list things) and no when-not guidance.

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