Skip to main content
Glama

devops-linux

github_actions_expression_eval

Evaluate GitHub Actions ${{ ... }} conditional expressions against simulated github/env/inputs contexts with contains(), startsWith(), success(), and boolean logic.

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

Input Schema

NameRequiredDescriptionDefault
textNo
contextNoSimulated context object { github: {...}, env: {...}, inputs: {...} }.
expressionNoe.g. "${{ github.ref == 'refs/heads/main' && !github.event.pull_request }}"

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?

With no annotations supplied, the description carries the full behavioral burden. It usefully discloses that contexts are simulated (no live GitHub API call) and names the supported function set, but omits the result shape (presumably a boolean but unstated) and the error behavior for invalid syntax or unsupported operators.

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; the verb and supported functions come first. Slightly dense packing of function names and context keys, but nothing is wasted and no sentence is redundant.

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?

There is no output schema, so the description should say what comes back (boolean, error detail, coerced truthiness of non-boolean values) and it does not. Combined with the unresolved text-vs-expression distinction, an agent can call it but may guess wrong about arguments and result handling.

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 67%, so a baseline of 3 is defensible. The description adds meaning for the context object by naming the github/env/inputs keys, matching the schema, but the crucial ambiguity remains unresolved: there are two string parameters, 'text' and 'expression', and nothing says which one carries the ${{ ... }} string versus a bare condition body.

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 and resource: 'Evaluate GitHub Actions ${{ ... }} conditional expressions'. It also scopes the input domain (simulated github/env/inputs contexts) and lists supported constructs (contains(), startsWith(), success(), boolean logic), which is enough for an agent to distinguish this from every sibling auditing/linting tool in the list.

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: an agent can infer this is for testing a workflow expression before committing it, since contexts are 'simulated' rather than live. The description never states when to prefer this over reading the workflow file, gives no prerequisites or exclusions, and does not mention what happens with an unsupported function or malformed expression.

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