Skip to main content
Glama
impossiblecode

overseer-nvim-mcp

Run a command as an overseer task

overseer_run

Start long-running commands (dev servers, file watchers, watch tests) as overseer tasks, so they appear in your task list and can be stopped when needed.

Instructions

Start a long-running command as an overseer task, so it appears in the user's task list, can be stopped from it, and inherits proper process-group teardown. Use for commands that DO NOT exit on their own: dev servers, file watchers, --watch test runs, log tails. For short commands that terminate by themselves, use Bash instead: you need their output in-band, and round-tripping a fast build through start-then-poll is worse. Pass exactly one of template or cmd. Prefer template (a name from overseer_list_templates) when one matches what you want; it runs the repo's own definition under the name the user already sees in their task list. Most repos declare no templates, in which case pass cmd as an argv array, which works anywhere. Note a cmd is a one-off, though: gone when the session ends, and the user cannot run it again without you. If they want it to persist, it belongs in a directory-local template instead of being re-passed as cmd every time; the server instructions describe how. cmd does not go through a shell, so for pipes, globs, && or env prefixes pass an explicit wrapper: ["sh", "-c", "..."]. Returns once the task has produced output or exited, up to settle_ms (default 1500, 0 to return immediately), so a command that dies on startup reports its failure here rather than looking identical to a healthy one until some later tail. Templates that declare params need them supplied here; pass params as an object of name to value. A missing required param comes back as an error naming what it wanted rather than a prompt opening in the editor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cmdNo
cwdNoWorking directory for the task; for `template`, also the directory the template is resolved in. Defaults to nvim's cwd
nameNoTask-list name for a `cmd` task; defaults to the command. A `template` runs under its own name
paramsNo
templateNo
settle_msNo
Behavior5/5

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

The description discloses many behavioral traits beyond the minimal annotations: the task appears in the task list, can be stopped, inherits teardown, `cmd` bypasses the shell, the call blocks until output/exit up to `settle_ms`, startup failures are reported, and missing required template params return an error. This is rich context not present in the annotation.

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?

Although the description is long, it is densely packed with necessary information and each sentence addresses a distinct concern: use case, alternative, parameter selection, persistence, shell behavior, return behavior, and error handling. It is front-loaded with purpose and usage, and there is no 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?

Given the tool's complexity (6 parameters, nested objects, template vs cmd alternatives, no output schema), the description is complete enough for an agent to select and invoke it correctly. It covers prerequisites, side effects, return semantics, failure handling, and persistence, leaving no significant operational gap.

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

Parameters5/5

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

Schema coverage is only 33%, but the description compensates by explaining the key parameters: `template` vs `cmd` exclusivity, `cmd` as an argv array not through a shell, `params` as a name-to-value object for templates, and `settle_ms` default and zero behavior. It also clarifies `cwd` resolution for templates beyond 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 ('Start a long-running command as an overseer task') and clearly differentiates the tool from siblings by stating what it does that others don't: appear in the user's task list, be stoppable, and get proper process-group teardown. It also contrasts with Bash for short commands, which removes ambiguity.

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 guidance is given on when to use this tool vs alternatives: use for commands that do not exit on their own, use Bash for short terminating commands. It further instructs when to prefer `template` over `cmd`, how to handle shell features with `sh -c`, and warns about `cmd` being a one-off, with an alternative for persistence.

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/impossiblecode/overseer-nvim-mcp'

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