Skip to main content
Glama

GitHub Actions for AI agents

find_github_actions
Read-only

GitHub Actions that run a coding agent in CI (Claude Code, Codex, Gemini CLI), review pull requests, test AI features or scan agent setups: the line to add, the secrets it reads, its license, and how many public projects set up for AI coding agents use it (AgentGid's scan of their workflows).

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

Input Schema

NameRequiredDescriptionDefault
groupNo
queryNoWhat it should do, e.g. 'review pull requests', 'run claude code', 'test prompts'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description does add genuinely useful behavioral context about what each result carries — the YAML line to add, the secrets it reads, its license, and adoption counts from AgentGid's workflow scan — but it says nothing about result limits, ranking, or empty-result behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The whole definition is a single run-on sentence with a colon that pivots mid-thought from what the tool finds to what a result contains. The purpose is front-loaded, but the return-value clause is jammed in without structure, and no sentence signals the parameter choices.

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?

With only two optional parameters and no output schema, the description does the right thing by describing what a returned entry includes. However, it leaves the group enum values undefined and gives no sense of result volume or how to broaden a query, which matters for a zero-required-parameter discovery tool.

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 coverage is 50%: the query parameter is documented in-schema ('review pull requests', 'run claude code'), but group has only bare enum values with no explanation. The description partially compensates by voicing the themes (agents-in-ci, review, testing, security, scan agent setups), letting an agent map a need to a group, though it never explicitly ties those words to the enum keys.

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 names a specific resource (GitHub Actions) and enumerates what those actions do — run coding agents in CI, review pull requests, test AI features, scan agent setups — so an agent can tell this is a discovery/search tool for CI workflow actions rather than for APIs or MCP servers. It never explicitly contrasts itself with the find_* siblings, and the second half drifts into describing result fields, which dilutes the purpose statement.

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?

There is no statement of when to reach for this tool versus find_apis, find_mcp_servers, or find_skills, and no exclusions or prerequisites. Usage is only inferable from the topic words ('GitHub Actions ... in CI'), which is guidance by implication rather than instruction.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources