Skip to main content
Glama

GitHub Actions Version Check

Check a workflow uses: line

check_action
Read-onlyIdempotent

Compare a uses: value (e.g. actions/checkout@v3) with the action's latest release: majors behind and the tag to use.

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": {
      "uses": "<uses>"
    },
    "name": "check_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
usesYes

Output Schema

NameRequiredDescriptionDefault
latestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description adds only the shape of the result (majors behind, recommended tag); it says nothing about failure behavior for unknown or private actions, rate limits, or whether resolution happens locally — gaps worth noting given openWorldHint=false.

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?

A single front-loaded sentence with no filler, and the input-then-output framing is easy to parse. The closing phrase 'the tag to use' is slightly loose but costs little.

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?

An output schema exists, so return values need not be spelled out, and the description is reasonable for a one-parameter read-only tool. However, edge cases such as an unrecognized action reference or a non-release tag are unaddressed, which leaves the definition only minimally complete.

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 description coverage is 0%, so the description must carry the parameter meaning — it does so partially by giving the concrete format example 'actions/checkout@v3'. It does not address the 5–200 character constraints, whether a SHA pin is accepted, or whether a version suffix is required.

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 verb ('Compare') and specific inputs and outputs: a `uses:` value versus the action's latest release, yielding 'majors behind and the tag to use'. That is far more concrete than a restatement of the name. It does not explicitly distinguish itself from the sibling `latest_action`, so a 4 rather than a 5.

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?

The use case (auditing a pinned action against its latest release) is implied clearly enough to act on, but there is no explicit when-to-use guidance and no statement of when to prefer `latest_action` instead. The agent must infer the split between the two tools.

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