Skip to main content
Glama
drewsonne

ruff-mcp-server

by drewsonne

pytest_runner

Run pytest tests on files, functions, or entire test suites with options for verbosity, markers, and failure handling.

Instructions

Run pytest tests on specific files, test functions, or entire test suite

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoPath to test file or directory (optional, defaults to current directory).
captureNoCapture mode: 'no' (disable), 'sys' (capture stdout/stderr), 'fd' (capture file descriptors)sys
markersNoRun tests with specific markers (e.g., '-m slow' or '-m "not slow"')
maxfailNoStop after N test failures
verboseNoRun with verbose output (-v flag)
extra_argsNoAdditional pytest arguments
test_classNoSpecific test class to run (e.g., 'TestMyClass')
last_failedNoRun only tests that failed in the last run (--lf flag)
collect_onlyNoOnly collect tests, don't run them (--collect-only flag)
failed_firstNoRun failed tests first, then remaining tests (--ff flag)
test_patternNoTest pattern to match (e.g., 'test_*_integration')
very_verboseNoRun with very verbose output (-vv flag)
test_functionNoSpecific test function to run (e.g., 'test_my_function')
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states 'Run pytest tests' without disclosing behavioral traits such as side effects (e.g., no file modification), required dependencies, or how results are returned. The description adds minimal insight beyond the name.

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?

The description is a single concise sentence with no wasted words. It is front-loaded with the core action and resource.

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?

Given the tool has 13 optional parameters and no output schema, the description is too minimal. It does not explain how parameters interact (e.g., test_function vs test_class), default behavior when no parameters are provided, or what the output looks like. For a complex testing tool, more detail is needed.

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 does not elaborate on parameter meanings beyond what the schema already provides, nor does it explain relationships or typical usage patterns. It adds no extra value.

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 action ('Run pytest tests') and the resource ('specific files, test functions, or entire test suite'), distinguishing it from the sibling ruff_* tools which are for linting and formatting.

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?

No guidance on when to use this tool versus alternatives. While the purpose distinguishes it from siblings, there is no mention of prerequisites, context, or when not to use it (e.g., if pytest is not installed).

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/drewsonne/ruff-mcp-server'

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