Skip to main content
Glama
mcp-github-project-manager

mcp-github-project-manager

by kunwarVivek

Discover Tools

discover_tools
Read-onlyIdempotent

Find available compound tools, their actions, and parameters by domain or free-text query to identify the right GitHub project management operation.

Instructions

Discover available compound tools, their actions, and parameters. Always available regardless of group filter.

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": "discover_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoFree-text search across tool names and descriptions
domainNoFilter tools by domain

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.0.0
    • changedInput schema / properties / domain / enum
      Previous value: -[
      -  "projects",
      -  "issues",
      -  "pull_requests",
      -  "milestones",
      -  "sprints",
      -  "labels",
      -  "automation",
      -  "iterations",
      -  "events",
      -  "status_updates",
      -  "ai_generation",
      -  "ai_analysis",
      -  "ai_planning",
      -  "agents",
      -  "system"
      -]New value: +[
      +  "projects",
      +  "issues",
      +  "pull_requests",
      +  "milestones",
      +  "sprints",
      +  "labels",
      +  "automation",
      +  "iterations",
      +  "events",
      +  "status_updates",
      +  "analytics",
      +  "ai_generation",
      +  "ai_analysis",
      +  "ai_planning",
      +  "agents",
      +  "system"
      +]
  2. Addedv3.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds one genuinely useful behavioral fact, that the tool remains callable regardless of group filters, but says nothing about result size, pagination, or how actions are grouped in the response.

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 short sentences, zero filler, with the core purpose stated first and the availability caveat second. Nothing to trim.

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?

For a two-optional-parameter read-only discovery tool with no output schema, the definition covers purpose, scope of results, and availability. The main remaining gap is the shape and volume of the returned tool catalogue, which an agent building a plan would benefit from knowing.

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% and both parameters carry their own descriptions plus a 16-value domain enum, so the schema does all the parameter work. The description adds no syntax, matching behavior, or interaction detail (e.g., whether query and domain combine) beyond 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 (discover) and resource (available compound tools) plus what the results contain: actions and parameters. This clearly differentiates it from every manage_*/ai_* sibling, which perform actions rather than enumerate them, though it never names a sibling explicitly.

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 only usage signal is 'Always available regardless of group filter,' which tells the agent the tool is never gated but not when to reach for it (e.g., before invoking an unfamiliar compound tool) or when the query/domain filters should be preferred over listing everything.

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