Skip to main content
Glama

megalinter_run

Run MegaLinter linting with advanced configuration options including flavor, release, fixes, and environment variables for full low-level control.

Instructions

Run Ox Security MegaLinter using mega-linter-runner with full low-level control. For short prompts, use megalinter_quick_action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workingDirectoryNoDirectory where the command is executed. Defaults to current process directory.
pathNoDirectory path to lint.
flavorNoMegaLinter flavor.all
releaseNoMegaLinter Docker image tag.v9
imageNoOptional full Docker image override.
envNoEnvironment variable string passed to --env (for example: DISABLE_LINTERS=SPELL_CSPELL,MARKDOWN_MARKDOWNLINT).
fixNoApply auto-fixes.
helpNoShow mega-linter-runner help.
installNoGenerate MegaLinter starter config files.
containerNameNoOptional Docker container name.
removeContainerNoRemove container after completion.
configFileNoPath to .mega-linter.yml file.
reportsPathNoDirectory where reports are written.megalinter-reports
disableLintersNoComma-separated list of linters to disable.
lintChangedFilesOnlyNoIf true, sets VALIDATE_ALL_CODEBASE=false to lint only changed files.
runnerVersionNomega-linter-runner npm version. Use 'latest' or a specific version.latest
timeoutSecondsNoCommand timeout in seconds.
summaryOnlyNoReturn concise logs instead of full stdout/stderr output.
extraArgsNoAdditional CLI arguments to append.
Behavior2/5

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

No annotations provided, so the description carries the full burden. It lacks behavioral traits such as whether it modifies files, authentication requirements, or rate limits. 'Full low-level control' is vague.

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 concise sentences, front-loaded with purpose and sibling distinction. No wasted words.

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?

With 19 parameters, 100% schema coverage, no output schema, and no annotations, the description is minimal. It achieves basic completeness but lacks behavioral guidance; the agent would rely heavily on parameter names and schema descriptions.

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%, so baseline is 3. The description adds no parameter-level detail beyond the schema; it only provides a high-level summary.

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?

The description clearly states the tool runs Ox Security MegaLinter with full low-level control, and explicitly distinguishes it from the sibling tool 'megalinter_quick_action' for short prompts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a clear context for when to use this tool (full low-level control) vs. a simpler alternative (megalinter_quick_action for short prompts). However, no explicit when-not or exclusion criteria for other siblings.

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