Skip to main content
Glama

delegate_task

Offload work to a cheaper model or summarize large vault files. Small files return directly; large files are delegated for summarization, falling back to raw content if workers are unavailable.

Instructions

Offload work to a cheaper model or summarize vault files.

When project is provided, reads a vault file. Small files (≤50 lines) are returned directly. Large files are auto-delegated to a worker for summarization — falls back to raw content if workers are unavailable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoRelative path to a .md file. Overrides section.
modelNoConcrete model id. Empty uses the configured worker model. The 4.0.0 removal retired 'auto', 'ollama', 'openrouter-free' and 'openrouter'; passing one is rejected rather than ignored.
promptNoThe task description or code to process.
contextNoOptional system context for the model.
projectNoProject slug for vault summarization mode.
sectionNoShortcut name for summarization. Ignored if path is set.context
timeout_sNoPer-dispatch deadline in seconds. 0 uses the ambient tool timeout. A value ABOVE the ambient one raises the ceiling rather than being clamped by it — a deadline a 60s default can silently cap is not a deadline (HIVE-384 AC3).
max_tokensNoMaximum tokens in the response.
structuredNoReturn a JSON record instead of prose. Prose is the default so every existing caller's contract is unchanged; the dispatcher asks for JSON because it needs the status as a VALUE. Exception types do not survive the JSON-RPC boundary between the daemon and its clients, so "the pool refused" and "the worker answered badly" cannot be told apart by type on the far side — and a dispatcher that cannot tell them apart turns a rate limit into a silent retry against a different model.
max_summary_linesNoTarget summary length for summarization.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The annotations provide no safety disclosure, but the description adds useful behavioral detail beyond them: the 50-line threshold, automatic worker delegation, and fallback behavior. It also clarifies the tool mutates nothing structurally while it performs offloading, though it doesn't fully explain side effects or costs.

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 entire description is two sentences that front-load the key action and immediately provide the most important behavioral caveat. No word is wasted, and the format is easy to grasp.

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

Completeness4/5

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

The description covers the main usage modes, file-size behavior, and fallback. With an output schema and full parameter descriptions present, this is sufficient for basic invocation, but it does not explain the generic no-project delegation mode clearly, so it is not a 5.

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 tool description does not need to document parameters. The main description only associates project with vault reading, but availing of the expected baseline: since the schema already covers 10 parameters, the description adds little beyond that.

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

Purpose4/5

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

The opening line 'Offload work to a cheaper model or summarize vault files' names a clear verb and resource, so an agent can understand the tool's purpose immediately. It does not explicitly name or distinguish itself from siblings like vault_ask or worker_status, so it's not quite a 5.

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

Usage Guidelines4/5

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

The description gives concrete execution context: it states that when project is provided a vault file is read, files ≤50 lines are returned directly, larger files are delegated to a worker, and there is a fallback if workers are unavailable. It does not provide explicit when-not-to-use guidance or alternatives, so it stops short of 5.

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/mlorentedev/hive'

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