Skip to main content
Glama

Ravi CI Guard: GitHub Actions security audit

Score your workflows (free)

peek_workflows
Read-only

FREE. Score (0-100), grade and finding counts by severity and rule for your workflows: repo=owner/name, url= one workflow file, or yaml= pasted text. Counts only: the line-by-line findings, fixes, SHA pins and git-apply patches come from audit_workflows.

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": "peek_workflows"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoOptional branch, tag or commit SHA for repo (default: the default branch)
urlNoAlternative: https URL of one workflow file (github.com blob/raw, raw.githubusercontent.com, gist)
repoNoPublic GitHub repository, owner/name or https://github.com/owner/name
yamlNoAlternative: the workflow file text itself (up to 64 KB)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations give readOnlyHint=true and openWorldHint=true; the description adds non-obvious behavior beyond them — that the tool is free (no payment/credits consumed) and that it returns counts only, no per-line detail or patches. That 'counts only' boundary is the single most decision-relevant trait here. It stops short of stating rate limits or how large repos trigger truncation.

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?

Two sentences, zero filler. 'FREE' and the counts-only limitation are front-loaded where an agent will see them first, with the routing to audit_workflows trailing as supporting context.

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?

There is no output schema, and the description compensates by naming what comes back (score 0-100, grade, finding counts by severity and rule). Combined with the 100%-covered input schema and the read-only annotation, an agent has almost everything needed; only return-format specifics like pagination or ordering are absent.

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 schema already labels url and yaml as 'Alternative:', so the description is largely restating it. It does reinforce that the three modes are mutually exclusive by joining them with 'or', and clarifies url means exactly one workflow file, but adds no format or edge-case guidance beyond the schema.

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 with output shape: 'Score (0-100), grade and finding counts by severity and rule for your workflows.' It also explicitly marks itself as the shallow, counts-only tier versus audit_workflows, so an agent can separate 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?

Names the alternative ('audit_workflows') and the precise condition that selects it: line-by-line findings, fixes, SHA pins and git-apply patches. It also enumerates the three accepted input modes (repo, url, yaml), which is the practical when-to-use condition for this tool.

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