Skip to main content
Glama

GitHub Actions Version Check

Latest version of a GitHub Action

latest_action
Read-onlyIdempotent

Latest release tag and major tag (e.g. v6) of an action like actions/checkout.

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": {
      "action": "<action>"
    },
    "name": "latest_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesowner/repo, e.g. actions/setup-node

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, idempotentHint, and closed-world behavior, so the safety profile is fully covered. The description adds the shape of the returned data (release tag plus major tag) but says nothing about failure modes, e.g. a repo with no releases or a nonexistent action.

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 with zero waste; the returned values come first and the example clarifies format immediately.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one required parameter, full schema coverage, an output schema, and rich annotations, the description is appropriately lean. It slightly under-delivers on edge-case behavior for a nonexistent or release-less action, but nothing essential for a correct call is missing.

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 100% and the single 'action' parameter is documented as owner/repo with a format example. The description's 'actions/checkout' example merely echoes the schema example rather than adding new meaning such as case sensitivity or whether a leading slash is tolerated.

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+resource: it returns the latest release tag and major tag for a named GitHub Action, with a concrete example ('actions/checkout', 'v6'). An agent can tell what it yields without opening the schema. It does not, however, distinguish itself from the sibling check_action.

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 explicit when-to-use or when-not guidance and no mention of the alternative check_action. The usage context (resolving a version to pin) is only inferable from the purpose statement itself.

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