Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Delimit Test Smoke

delimit_test_smoke
Read-onlyIdempotent

Run smoke tests before commit or deploy to confirm the project test suite passes. Auto-detects pytest, Jest, Vitest, or Mocha from project config and reports failures, with options to stop at the first error or target a specific suite.

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
fail_fastNoStop execution immediately on first failure.
extra_argsNoOptional extra arguments to pass to the test runner.
test_suiteNoOptional specific test suite or pattern.
project_pathYesProject path. Required.
timeout_secondsNoOptional execution timeout in seconds. Default is 120.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv4.7.9
    • addedInput schema / properties / extra_args
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional extra arguments to pass to the test runner."
+}
    • addedInput schema / properties / fail_fast
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": false,
+  "description": "Stop execution immediately on first failure."
+}
    • changedInput schema / properties / project_path / description
      Previous value: -"Project path."New value: +"Project path. Required."
    • changedInput schema / properties / test_suite / description
      Previous value: -"Specific test suite to run."New value: +"Optional specific test suite or pattern."
    • addedInput schema / properties / timeout_seconds
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": 120,
+  "description": "Optional execution timeout in seconds. Default is 120."
+}
  2. Changed2 schema fields changedv4.5.5
    • addedInput schema / properties / project_path / description
      Added value: +"Project path."
    • addedInput schema / properties / test_suite / description
      Added value: +"Specific test suite to run."
  3. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

The description goes beyond the annotations by disclosing that it invokes the project's test runner via backends.ui_bridge.test_smoke as a subprocess, and that it is read-only on the filesystem apart from the test runner's own outputs. This adds meaningful operational context that the annotations do not fully convey.

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 well-structured with clear sections for use cases, non-use cases, sibling contrast, and side effects. Each section earns its place and the core purpose is front-loaded in the first sentence.

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?

The description covers purpose, usage timing, alternatives, framework detection, side effects, and filesystem impact. With an output schema present and all parameters fully described in the schema, nothing essential is missing for an agent to correctly select and invoke this tool.

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 the schema already documents all five parameters and their defaults. The description adds general context like framework auto-detection but does not add much per-parameter meaning beyond what the schema provides, which matches the baseline of 3.

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 opens with a specific verb and resource: 'Run smoke tests for a project.' It further differentiates from siblings by stating delimit_test_generate writes, delimit_test_coverage measures, and this tool 'runs and parses,' leaving no ambiguity about its role.

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?

Explicit when-to-use guidance is provided: 'as a pre-commit / pre-deploy gate to confirm tests pass.' It also includes clear when-not-to-use instructions with named alternatives for scaffolding tests and measuring coverage, making the routing decision unmistakable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools