Skip to main content
Glama

Tack

Look up GitHub Actions: latest release, commit SHA, runtime and inputs (live)

tack_resolve_actions
Read-onlyIdempotent

Use when a uses: line for a GitHub Action is about to be written and its current version, commit SHA or inputs are needed, or the user asks what the latest version of an action is, what SHA a tag points to, or whether an action or tag exists (signals: "latest actions/checkout", "pin setup-node to a SHA", "what inputs does this action take", "does v9 exist", "which version is this SHA"). Takes owner/repo (latest release), owner/repo@ref or owner/repo/path@ref, reads the tags and branches live from github.com and the action.yml at that commit, and returns per action: exists or not, the commit SHA, the release a SHA or major tag points to, the latest release and major tag, runs.using (flags node20 and older, which GitHub stopped shipping on 2026-09-23), retired versions that fail jobs, the declared inputs, and a ready-to-paste line: uses: owner/repo@<40-char sha> # vX.Y.Z. Example: {"actions":["actions/checkout","actions/setup-node@v4","docker/build-push-action@v6"]}. Up to 30 per call. Public github.com repositories only; for a whole workflow file use tack_check_workflow.

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": {
      "actions": "<actions>"
    },
    "name": "tack_resolve_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionsYesAction references: "owner/repo" (latest release), "owner/repo@v4", "owner/repo/path@ref", or a full uses: line.
upgradeNoFor references with a ref, return the pinned line for the latest release instead. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds substantial context beyond them: it reads live from github.com rather than a cache, is restricted to public github.com repositories, caps at 30 references per call, and flags node20-and-older runtimes plus retired versions that fail jobs. It also enumerates the return payload per action, including a ready-to-paste pinned uses: line.

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

Conciseness4/5

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

Front-loaded with the trigger condition and well organized as purpose, mechanics, return payload, example, limits, and exclusion. The middle mechanics sentence is a long multi-clause run-on that could be broken up, but nearly every clause carries distinct information rather than filler.

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?

There is no output schema, so the description must describe return values, and it does in detail (existence, SHA, release mapping, latest major tag, runs.using, retired versions, declared inputs, paste-ready line). Scope limits, batch size, and the sibling boundary are also covered, leaving nothing an agent needs in order to call it 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 the baseline is 3, but the description adds real value: it enumerates the accepted reference shapes (owner/repo, owner/repo@ref, owner/repo/path@ref, full uses: line) and gives a literal example payload. The `upgrade` parameter is only covered by the schema, not the description, which keeps this just below a 5.

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 concrete verb and resource: resolves GitHub Action references to current version, commit SHA, runtime and inputs, reading tags/branches live from github.com. It also names the sibling it is not ("for a whole workflow file use tack_check_workflow"), so an agent can route between the two without opening either schema.

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 trigger ("when a uses: line ... is about to be written"), lists concrete user-phrase signals such as "pin setup-node to a SHA" and "does v9 exist", and gives an explicit exclusion pointing to tack_check_workflow for whole files. When-to-use, when-not-to-use, and the alternative are all present.

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