Skip to main content
Glama

megalinter_quick_action

Perform quick code scans, security analyses, and error summaries. Configure MegaLinter and parse SARIF reports with short instructions.

Instructions

Interactive shortcut tool for short requests (for example: quick scan, security scan, summarise errors, list python security linters).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestNoShort instruction. Examples: quick scan, full scan, security scan, summarise errors, parse sarif report, write config.quick scan
actionNoOptional explicit action. Use this for deterministic quick workflows.
scanModeNoScan preset when action is scan (or request implies a scan).
targetNoDirectory to scan for run requests. Defaults to .
workingDirectoryNoDirectory where commands run. Defaults to current process directory.
reportsPathNoReport directory for parse, summary, and recommendation requests.megalinter-reports
reportTypeNoReport format for parse requests. Defaults to json unless sarif is requested.
severityNoSeverity filter for summary requests.
linterFilterNoLinter filter for summary requests.
languageNoLanguage filter for linter-list requests. For scans, this maps to a flavor hint (e.g., python -> python, typescript -> javascript).
securityOnlyNoFilter linter-list requests to security linters. For scans, forces security flavor.
autoFixOnlyNoFilter linter-list requests to auto-fix linters.
timeoutMinutesNoRun timeout in minutes for scan requests.
summaryOnlyNoUse concise output for scan requests. Set false for full logs.
flavorNoOptional flavour override for scan requests (e.g., javascript, python, security).
fixNoForce auto-fix for scan requests.
targetPathNoOutput file path for write-config requests. Defaults to .mega-linter.yml.
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only describes the tool as 'interactive shortcut' without mentioning side effects, permissions, or whether operations are read-only or mutating. This is insufficient for safe agent invocation.

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?

The description is concise—one sentence plus examples—and front-loaded with the core purpose. It avoids unnecessary elaboration while still being informative.

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

Completeness2/5

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

Despite the schema covering parameter descriptions, the tool description is too brief for a tool with 17 parameters and no output schema. There is no explanation of interactions between parameters (e.g., how 'request' and 'action' relate), default behaviors, or error handling. This leaves gaps for effective use.

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 100% with detailed parameter descriptions. The tool description adds high-level context (e.g., examples mapping to parameters) but does not significantly enhance understanding beyond what the schema provides. Baseline 3 is appropriate.

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 clearly identifies this as an 'interactive shortcut tool for short requests' and provides concrete examples (quick scan, security scan, summarise errors). This distinguishes it from sibling tools like megalinter_run which handles full runs, though the differentiation is not explicitly stated.

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 description implies use for short requests but does not provide explicit guidance on when to use this tool vs. alternatives such as megalinter_run or scan. No 'when not to use' information is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DownAtTheBottomOfTheMoleHole/megalinter-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server