Skip to main content
Glama

Tack

Check a GitHub Actions workflow and pin every action to a commit SHA (live)

tack_check_workflow
Read-onlyIdempotent

Use when the user asks to write, review, fix or harden a GitHub Actions workflow (.github/workflows/*.yml) or a composite action.yml, or when a workflow was just written or edited and is about to be committed (signals: "write a CI workflow", "why does my workflow fail", "Invalid workflow file", "Unexpected input", "pin actions to SHA", "is actions/checkout@v4 still current", "Node 20 deprecated", "upload-artifact v3", "runs-on ubuntu-20.04", "script injection", "pull_request_target"). Parses the YAML (errors with line and column, duplicate keys, anchors), checks the structure against GitHub's workflow syntax as documented on 2026-11-19 (including recent keys such as schedule timezone, cache-mode, background, wait, wait-all, cancel, parallel and $/ self-repository references), then resolves every uses: reference live on github.com: whether the repository, tag, branch or commit exists, which release a SHA is, the latest release, retired versions that make a job fail (upload/download-artifact v3 and older, actions/cache v1-v2 and old exact pins), runs.using node20-or-older runtimes, with: inputs the action does not declare (with a did-you-mean), missing required inputs, reusable-workflow inputs, and pinned-SHA comments that name the wrong version. Also flags retired runner labels (live runner-images list), script injection through ${{ github.event... }} in run:, pull_request_target checkouts of PR code, and a missing permissions key. Returns each finding with line, path, fix and doc link, per-action resolution, fix_message, and pinned_workflow: the same file with every action pinned to its full commit SHA and a # version comment (retired or missing refs move to the latest release; upgrade:true moves all). Example: {"workflow":"on: push\njobs:\n test:\n runs-on: ubuntu-latest\n steps:\n - uses: actions/checkout@v4\n - uses: actions/setup-node@v4\n with:\n node_version: 20"}. Does not run the workflow, evaluate expressions or see private repositories, secrets or repository settings. Up to 200000 characters.

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": {
      "workflow": "<workflow>"
    },
    "name": "tack_check_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoauto (default) detects a workflow (jobs:) or an action metadata file (runs:).
liveNoResolve actions, inputs and runner labels on github.com. Default true; false = offline YAML and syntax checks only.
upgradeNoPin every action to its latest release instead of the version the file uses. Default false (retired or missing refs are moved to the latest release either way).
workflowYesThe YAML text of a workflow file (.github/workflows/<name>.yml) or of an action.yml / action.yaml.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive, and the description still adds substantive behavior: it performs live resolution on github.com, honors a 200000-character input cap, moves retired or missing refs to the latest release even when upgrade is false, and returns a rewritten file rather than writing one. What it leaves out is failure behavior when live resolution is unavailable and whether findings are sorted or paginated.

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

Conciseness3/5

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

The triggering clause is correctly front-loaded and every block carries information, but the body is a single dense run-on sentence packing syntax keys, live-resolution checks, security checks and output shape into one breath. A short bulleted split of checks vs. return values would be easier to scan without losing content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries the return contract and does so fully: findings with line, path, fix and doc link, per-action resolution, fix_message, and pinned_workflow containing the same file with SHA pins and version comments. Combined with the exclusion list (no private repos, no secrets, no execution), an agent has everything needed to call it and interpret the result.

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 coverage is 100%, so baseline is 3, but the description adds real meaning beyond the schema: it explains that upgrade:true moves all actions to latest (vs. only retired/missing refs otherwise), that live:false reduces to offline YAML and syntax checks, and it shows kind auto-detection by the jobs: vs runs: marker. It gives a worked example of the workflow text.

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 and resource: parses workflow/action YAML, checks it against GitHub syntax, resolves every uses: reference live, and returns findings plus a pinned_workflow. An agent can tell exactly what it produces. It never names the sibling tack_resolve_actions, which also resolves action references, so the scope boundary between the two is left implicit.

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?

Opens with an explicit when-to-use clause covering workflow or action.yml authoring, review, fixing and pre-commit checks, backed by concrete trigger phrases ("Invalid workflow file", "pin actions to SHA", "script injection", "pull_request_target"). It also states exclusions clearly: it does not run the workflow, evaluate expressions, or access private repos, secrets or repository settings.

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