Skip to main content
Glama

Ravi CI Guard: GitHub Actions security audit

List the checks (free)

list_rules
Read-only

FREE. The rule families CI Guard checks, with one line each, and the methodology.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description's burden is lower. It adds genuinely non-structured information: the call is free of charge and returns a compact one-line-per-family listing plus methodology prose, which tells the agent the payload is small reference text rather than data to be parsed.

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?

One short sentence plus a front-loaded "FREE." marker; every clause carries information about cost or return shape. Nothing is padded and the most decision-relevant fact (zero cost) comes first.

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?

For a parameterless, read-only reference tool with no output schema, the description covers what is returned and at what granularity (one line per rule family, plus methodology), and the annotations cover the safety profile. It stops short of explaining what "the methodology" section contains, which is the only remaining ambiguity.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly implies the call is unconditional and unfiltered, with nothing for the agent to supply or misconfigure.

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 the specific resource: the rule families CI Guard checks, each on one line, plus the methodology. There is no explicit verb, but the noun phrase plus the title make the returned content unambiguous, and an agent can tell this is a static catalog rather than a scanning action. It does not distinguish itself from siblings, but the siblings listed are audit/payment tools with clearly different subjects.

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 when-to-use or when-not-to-use guidance; the only implicit cue is the leading "FREE," which signals this is a cheap exploratory call. Nothing tells the agent whether this should be called before an audit, or how it relates to audit_workflows or peek_workflows.

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