Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

delimit_agent_dispatch

Record an engineering-task dispatch intent with audit trail. Assign tasks, set constraints, and document context for replay, without running the work.

Instructions

Record an engineering-task dispatch with full audit trail (Pro).

When to use: as the PLANNING + AUDIT surface when the orchestrator decides to delegate parallelizable engineering work to a subagent. Per the operating model (2026-05-01 revision), actual execution is performed by the Agent tool with subagent_type=engineering; this tool records the intent, assignee, constraints, and eventual outcome so the dispatch is replayable from the ledger. When NOT to use: as an autonomous queue processor expecting auto-execution — this records dispatch but does NOT run the work. Real autonomous queue execution is deferred to a future capability (LED-193 daemon) with strict sandboxing + founder- approval semantics. Also do not use for conversational tasks, sub-5-minute work, or work where no function exists yet.

Sibling contrast: delimit_agent_status reads dispatched task state; delimit_agent_handoff transfers a recorded task to a different model; delimit_agent_complete closes the task with results. Compared to delimit_ledger_add, this is the engineering- work surface with assignee, tools_needed, and constraints schema; ledger items are free-form.

Side effects: writes a new task record to disk via ai.agent_dispatch.dispatch_task (a JSON record in the agent tasks file plus an audit log entry). String list inputs (tools_needed, constraints) are coerced from comma strings to lists. NO subagent is spawned by this call — the caller is responsible for invoking the Agent tool separately. Gated by require_premium — unlicensed callers receive a license payload.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesShort task title. Required.
descriptionNoLonger task description.
assigneeNoTarget model — "claude", "codex", "gemini", or "any". Default "any".any
priorityNoOne of "P0" (immediate), "P1" (default), "P2".P1
tools_neededNoComma-separated MCP tools the work will need.
constraintsNoComma-separated constraints (e.g. "no force push").
contextNoBackground info to seed the executor.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: writes to disk, coerces string inputs to lists, does NOT spawn subagent, is gated by require_premium. It covers side effects and limitations comprehensively.

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

Conciseness4/5

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

The description is well-structured with clear sections and is front-loaded with the main purpose. Though lengthy, each sentence adds value. Slightly verbose but still concise given the amount of information.

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?

Given 7 parameters with full schema coverage and no annotations, the description provides comprehensive context: behavior, side effects, usage conditions, and relation to siblings. It fully explains the tool's role and limitations.

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 baseline is 3. The description adds minimal meaning beyond schema defaults and enumerations. It repeats some parameter info but does not provide additional semantic depth.

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 clearly states the tool records an engineering-task dispatch with audit trail. It uses specific verb 'record' and resource 'engineering-task dispatch'. It distinguishes from siblings like delimit_agent_status, delimit_agent_handoff, delimit_agent_complete, and delimit_ledger_add.

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' and 'When NOT to use' sections provide clear guidance. It specifies appropriate contexts (planning and audit surface for delegating parallelizable work) and exclusions (autonomous queue, conversational tasks, sub-5-minute work, no existing function). Also contrasts with sibling tools.

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