Skip to main content
Glama

delimit_test_smoke

Run smoke tests to validate project builds and confirm tests pass before commit or deploy. Automatically detects pytest, jest, vitest, or mocha from project configuration.

Instructions

Run smoke tests for a project.

When to use: as a pre-commit / pre-deploy gate to confirm tests pass. Auto-detects framework (pytest / jest / vitest / mocha) from project config. When NOT to use: to scaffold new tests (use delimit_test_generate) or measure coverage (delimit_test_coverage).

Sibling contrast: delimit_test_generate writes; delimit_test_coverage measures; this runs and parses.

Side effects: invokes the project's test runner via backends.ui_bridge.test_smoke (subprocess). Read-only on filesystem apart from the test runner's own outputs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_pathYesProject path. Required.
test_suiteNoOptional specific test suite or pattern.
timeout_secondsNoOptional execution timeout in seconds. Default is 120.
extra_argsNoOptional extra arguments to pass to the test runner.
fail_fastNoStop execution immediately on first failure.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Discloses side effects (invokes test runner via subprocess, read-only on filesystem) and auto-detection of frameworks. Lacks some detail on failure handling or output format, but given no annotations, this is strong.

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?

Very concise and well-structured with separate sections for usage, exclusions, sibling contrast, and side effects. Every sentence adds value; no redundancy.

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

Completeness5/5

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

Covers all necessary aspects: purpose, when/not to use, side effects, and sibling distinction. Output schema exists, so return format explanation is not needed, making the description complete.

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 coverage is 100%, and parameter descriptions are sufficient. The description adds value with the auto-detection note but does not significantly enhance parameter understanding beyond the schema.

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?

Clearly states 'Run smoke tests for a project' with specific verb-run and resource-tests. Differentiates from siblings by naming delimit_test_generate and delimit_test_coverage, providing a precise contrast.

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

Usage Guidelines5/5

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

Explicitly defines when to use (pre-commit/pre-deploy gate) and when not to use (scaffolding tests, measuring coverage) with sibling alternatives. Offers unambiguous guidance.

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/delimit-ai/delimit-mcp-server'

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