Skip to main content
Glama

dart-run

Execute Dart scripts with specified arguments and working directory through the Dart MCP Server for AI-assisted development workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scriptYesPath to the Dart script to run
argsNoArguments to pass to the script
workingDirNoWorking directory for the command

Implementation Reference

  • The main handler function for the 'dart-run' tool. It runs the specified Dart script using 'dart run', handles paths, and returns stdout/stderr.
    export async function run({ 
      script, 
      args = [], 
      workingDir 
    }: z.infer<typeof runSchema>) {
      // Convert relative script path to absolute path
      const absoluteScript = toAbsolutePath(script, workingDir);
      
      // If workingDir is provided, ensure it's absolute
      const absoluteWorkingDir = workingDir ? toAbsolutePath(workingDir) : workingDir;
      
      const { stdout, stderr } = await executeDartCommand('run', [absoluteScript, ...args], absoluteWorkingDir);
      
      return {
        content: [
          { type: "text" as const, text: stdout || stderr }
        ],
        isError: !!stderr
      };
    }
  • Zod input schema for the 'dart-run' tool defining script path, optional arguments, and working directory.
    export const runSchema = z.object({
      script: z.string().describe('Path to the Dart script to run'),
      args: z.array(z.string()).optional().describe('Arguments to pass to the script'),
      workingDir: z.string().optional().describe('Working directory for the command')
    });
  • src/index.ts:41-41 (registration)
    Registers the 'dart-run' tool with the MCP server using the runSchema and run handler.
    server.tool('dart-run', runSchema.shape, run);
  • src/index.ts:23-23 (registration)
    Imports the run handler and runSchema from the tools/run module.
    import { run, runSchema } from './tools/run.js';
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