Skip to main content
Glama
Sign In
@sumirati/mcp-github

@sumirati/mcp-github

by sumirati
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Find GitHub Actions

github_find_actions
Read-onlyIdempotent

Search and discover available GitHub actions by keyword or domain filter, then retrieve action names, categories, and parameter signatures to build a valid execution call.

Instructions

Search and discover available GitHub actions in the 83-action catalog by keyword query or domain filter. Use this discovery tool first whenever you need to perform an action outside the 3 eager daily drivers (e.g. managing PRs, issues, releases, workflows, collaborators, webhooks, variables, security alerts). Returns matching action names, domain categories, mutating flags, descriptions, and parameter signatures so you can construct the call for github_execute_action.

Input Schema

NameRequiredDescriptionDefault
queryNoSearch keyword query to match against action names, domains, or descriptions (e.g. 'pull request', 'issue comment', 'webhook', 'deploy', 'dependabot')
domainNoOptional domain filter to restrict discovery to a specific functional category
formatYesOutput format: 'markdown' (default, compact human/LLM-readable text table) or 'json' (structured object with parameter schemas)markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.2.0
    • changedInput schema / properties / format / default
      Previous value: -"json"New value: +"markdown"
    • changedInput schema / properties / format / description
      Previous value: -"Output format: 'json' (default, structured object) or 'markdown' (compact human/LLM-readable text table)"New value: +"Output format: 'markdown' (default, compact human/LLM-readable text table) or 'json' (structured object with parameter schemas)"
  2. Addedv2.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered. The description adds catalog size (83 actions), the existence of 3 eager daily drivers, and the return payload (names, domains, mutating flags, descriptions, parameter signatures). This is useful behavioral context beyond annotations, though it doesn't cover rate limits or pagination.

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, front-loaded with the core purpose, then usage guidance. No wasted words.

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 discovery tool with 100% schema coverage and no output schema, the description covers purpose, usage, and return shape. It could be slightly more complete by explaining how results map to execution parameters, but it's sufficient for an agent 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 description coverage is 100%, so baseline is 3. The description adds meaning by mentioning 'keyword query or domain filter' and the return payload, but doesn't add syntax beyond the schema's examples. Slight uplift for clarifying the purpose of query and domain.

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+resource: 'Search and discover available GitHub actions in the 83-action catalog'. Differentiates from siblings by naming the catalog and indicating it's a discovery tool, while github_execute_action is the execution counterpart.

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?

Explicitly says 'Use this discovery tool first whenever you need to perform an action outside the 3 eager daily drivers' and lists example domains. Also states the downstream step: construct the call for github_execute_action, and mentions the 3 eager daily drivers as an alternative.

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