Skip to main content
Glama

dart-test

Run Dart unit tests by executing test files or directories with configurable options to verify code functionality during development.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoPath to the test file or directory
optionsNoAdditional test options
workingDirNoWorking directory for the command

Implementation Reference

  • The main handler function for the 'dart-test' tool. It executes the 'dart test' command with the provided path, options, and working directory, handling absolute paths and returning stdout/stderr.
    export async function test({ 
      path, 
      options = [], 
      workingDir 
    }: z.infer<typeof testSchema>) {
      // Convert relative path to absolute path if provided
      const absolutePath = path ? toAbsolutePath(path, workingDir) : undefined;
      
      // If workingDir is provided, ensure it's absolute
      const absoluteWorkingDir = workingDir ? toAbsolutePath(workingDir) : workingDir;
      
      const args = [
        ...(absolutePath ? [absolutePath] : []),
        ...options
      ];
      
      const { stdout, stderr } = await executeDartCommand('test', args, absoluteWorkingDir);
      
      return {
        content: [
          { type: "text" as const, text: stdout || stderr }
        ],
        isError: !!stderr
      };
    }
  • Zod schema defining the input parameters for the 'dart-test' tool: optional path, options array, and workingDir.
    export const testSchema = z.object({
      path: z.string().optional().describe('Path to the test file or directory'),
      options: z.array(z.string()).optional().describe('Additional test options'),
      workingDir: z.string().optional().describe('Working directory for the command')
    });
  • src/index.ts:42-42 (registration)
    Registers the 'dart-test' tool on the MCP server using the testSchema.shape and the test handler function.
    server.tool('dart-test', testSchema.shape, test);
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/egyleader/dart-mcp'

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