Skip to main content
Glama
Sign In
Git MCP Server

Git MCP Server

by EnesOzturk11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get All Issues

fetch_all_issues

Retrieve all issues from a specified remote GitHub repository and list them. Provide the repository owner and name to get a complete list.

Instructions

Get all issues from the specified remote repo and list them

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": {
      "repoName": "<repoName>",
      "repoOwner": "<repoOwner>"
    },
    "name": "fetch_all_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNameYesExact repo name for the url parameter. Ask the user if it is not provided.
repoOwnerYesExact repository owner for the url paramter that indicates what is the owber of the repo. Ask the user if it is not provided.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior, but it only says 'get all issues' without mentioning pagination, ordering, authentication, network dependency, or return format. This leaves significant behavioral traits undisclosed.

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?

The description is a single concise sentence with no unnecessary words. The phrase 'and list them' is slightly redundant but not wasteful.

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 two-parameter list tool, the description gives a basic sense of operation, but lacks details about output format, result size, or behavior such as whether it fetches from remote (network) and any prerequisites. Gaps remain.

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?

Both parameters are fully described in the schema (100% coverage), giving their meaning and asking user to provide if missing. The description adds no extra semantic value beyond the schema.

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?

The description clearly states the tool fetches all issues from a specified remote repository and lists them. This distinguishes it from sibling tools like fetch_merged_prs (PRs) and get_issue_comments (comments on a specific issue).

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 guidance is provided on when to use this tool versus alternatives like get_issue_comments or fetch_merged_prs. The description lacks context for selection among siblings.

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