Skip to main content
Glama

devops-linux

github_actions_audit

Parse GitHub Actions workflow YAML to extract jobs, triggers, matrix/needs DAG, unpinned third-party actions, and pull_request_target injection risks.

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_actions_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the analytical outputs in useful detail, and 'Parse'/'audit' implies a read-only static analysis with no mutation, but it never states side effects, whether the file is fetched from disk/network or requires auth, or how invalid YAML is handled.

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 where every clause names a distinct extracted artifact; no filler or redundancy.

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 no output schema, the description usefully enumerates the return content, which covers the output side well. However, for a two-input tool it omits how to supply input (raw text vs file path), which is the main missing piece an agent needs to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never mentions the 'text' or 'filePath' parameters. With two optional params and no explanation of precedence when both are supplied, or of which one is intended for the common case, an agent must guess the input mode.

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 ('Parse') and a specific resource ('GitHub Actions workflow YAML'), then enumerates exactly what it extracts: jobs, triggers, matrix/needs DAG, unpinned third-party actions, and pull_request_target injection risks. This is clearly separable from siblings such as gitlab_ci_audit (different CI system) and github_actions_expression_eval (expression evaluation, not workflow auditing).

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?

Usage is only implied: the description's risk-oriented output list signals it should be used to audit a workflow file for security/config issues. There is no explicit statement of when to prefer it over github_actions_expression_eval or gitlab_ci_audit, and no prerequisites or exclusions are given.

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