Skip to main content
Glama

Delimit Test Generate

delimit_test_generate

Generate test skeletons for source code with Jest, pytest, or vitest. Scaffold test stubs for untested public functions so you can begin testing a module without writing boilerplate.

Instructions

Generate test skeletons for source code (Jest / pytest / vitest).

When to use: to scaffold new test stubs for public functions when starting tests on a previously-untested module. When NOT to use: to measure coverage of existing tests (use delimit_test_coverage) or run a smoke test (delimit_test_smoke).

Sibling contrast: delimit_test_coverage measures; delimit_test_smoke runs; this writes new test scaffolds.

Side effects: writes new test files alongside the source. Uses AST parsing for Python and regex for JS/TS via backends.ui_bridge.test_generate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
frameworkNoTest framework — "jest" (default), "pytest", "vitest".jest
project_pathYesProject path. Required.
source_filesNoSpecific files to generate tests for. None = all detectable public functions.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv4.7.9
    • changedInput schema / properties / framework / description
      Previous value: -"Test framework (jest/pytest/vitest)."New value: +"Test framework — \"jest\" (default), \"pytest\", \"vitest\"."
    • changedInput schema / properties / project_path / description
      Previous value: -"Project path."New value: +"Project path. Required."
    • changedInput schema / properties / source_files / description
      Previous value: -"Specific files to generate tests for."New value: +"Specific files to generate tests for. None = all detectable public functions."
  2. Changed3 schema fields changedv4.5.5
    • addedInput schema / properties / framework / description
      Added value: +"Test framework (jest/pytest/vitest)."
    • addedInput schema / properties / project_path / description
      Added value: +"Project path."
    • addedInput schema / properties / source_files / description
      Added value: +"Specific files to generate tests for."
  3. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only provide readOnlyHint=false and destructiveHint=false. The description adds meaningful behavioral context by stating that the tool 'writes new test files alongside the source' and explains the parsing approaches for different languages. This goes beyond the structured fields without contradicting them.

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 tightly organized into labeled sections that are easy to scan. Every section earns its place: purpose, when to use, when not to use, sibling contrast, and side effects. It is long enough to be useful but not padded with filler.

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?

For a tool with an output schema and 100% schema coverage, the description covers the remaining contextual needs: selection criteria, exclusions, side effects, and implementation nuance. An agent has enough to decide when to invoke it and what to expect.

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 baseline is 3 and the schema already documents all three parameters. The description adds some framing like 'public functions' and framework names, but it does not meaningfully extend the parameter-level semantics provided in 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?

The description opens with a specific verb and resource: 'Generate test skeletons for source code (Jest / pytest / vitest).' It goes beyond a generic label by naming the frameworks and the artifact produced, and the sibling contrast explicitly distinguishes this tool from delimit_test_coverage and delimit_test_smoke.

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?

The description provides explicit 'When to use' and 'When NOT to use' sections, including concrete alternative tools for excluded cases. The sibling contrast further clarifies the division of labor, leaving no ambiguity about when to select this tool.

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