Executes pytest on a chosen path with optional extra arguments, letting you run targeted or full test suites and get results without leaving the workspace.
Run pytest on a path with optional extra args (e.g. '-k name -x').
| Name | Required | Description | Default |
|---|---|---|---|
| cwd | No | ||
| args | No | ||
| path | No | . |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is partly covered. However, the description adds no behavioral context such as test execution possibly being slow, executing arbitrary code, or how the working directory affects the run.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One efficient sentence with the core action front-loaded and a helpful example for args. No wasted words, though it omits the cwd parameter entirely.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be explained. But with cwd undocumented, no guidance against alternatives, and no behavioral details for a command-execution tool, the definition is not complete enough for reliable invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% for all three parameters. The description mentions path and args with a useful example ('-k name -x'), but leaves cwd completely unexplained and does not state defaults or how args are passed to pytest.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: run pytest on a path with optional extra args. It is clearly distinguishable from lint/format, but does not differentiate from run_command or other execution siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to prefer this over run_command or other execution tools, and no prerequisites or caveats about running tests in a workspace. The agent must infer usage entirely.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.