Python Lint Checker
python_lint_checkerStatic analysis for Python files — detects unused imports, likely bugs, style violations, and high-complexity functions. No code is executed. Use when: user asks to lint, review, check quality, or find bugs in Python code. Scope: Python files only (.py). Local files — no network access. Not for: other languages, package vulnerabilities (use dependency_audit), or secrets in files (use repo_scanner).
How to use python_lint_checker
Provide only the required inputs below. Start with the smallest scope that answers the task, then review the risk properties before an agent executes the call.
Risk and execution properties
Read only: yes
Destructive: no
Idempotent: yes
Open world: no — operates locally or through configured services
Inputs
pathstringrequiredPython file or directory to analyze. Example: '/Users/me/project/src'
checksstringComma-separated check categories to run: imports, bugs, style, complexity. Default: 'all'. Example: 'bugs,imports'
Default: "all"
max_line_lengthintegerMaximum line length before STY001 triggers. Default: 88 (matches black/ruff). Example: 120
Default: 88
max_findingsintegerMaximum number of findings to return. Summary counts are always complete. Default: 200. Use summary_only=true for large repos.
Default: 200
summary_onlybooleanReturn only summary counts — no per-file findings. Fast and compact for large repos. Default: false.
Default: false
Example input
{
"path": "<string>",
"checks": "all",
"max_line_length": 88,
"max_findings": 200,
"summary_only": false
}Browse or search the full 74-tool reference to choose the smallest suitable capability.
Browse all tools →