Skip to main content
Glama
plumbkit

plumb

Official
by plumbkit
OverviewSchemaRelated ServersScoreDiscussions
Go
Local

run_task

Run a stored per-language task—build, lint, test, e2e, verify, or custom—from the project config, with an optional safe target for scoping. Executes only pre-approved commands, no shell.

Instructions

Run a stored per-language task command — build, lint, test, e2e, verify, or a project-defined slot — configured in [tasks.]. It executes only the command the user saved for this workspace's language (no shell, no agent-supplied command line); the optional target fills a {target} placeholder with one shell-safe argument, and the shipped test defaults carry one so scoping needs no config edit. Commands run from the workspace root, or from [tasks.] working_dir when the module lives in a subdirectory. A project-supplied (.plumb/config.toml) command must be trusted first (run plumb trust); the shipped defaults and global-config commands always run. Output and runtime are bounded. Pairs with topology_affected (which says WHICH tests to run; this runs them).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slotNoWhich stored task command to run: build, lint, test, e2e, verify, or a project-defined slot under [tasks.<lang>]. session_start lists what's configured; an unconfigured slot is refused with that list.
targetNoOptional target substituted for a {target} token in the stored command (e.g. a single test name or package). The shipped go/python/rust test defaults carry a defaulted placeholder ({target:./...}), so scoping works with no config edit and omitting the target still runs everything. Restricted to one shell-safe argument ([A-Za-z0-9._/:@-]); refused if the command has no {target} slot.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.17.7
    • changedInput schema / properties / target / description
      Previous value: -"Optional target substituted for a {target} token in the stored command (e.g. a single test name or package). The shipped go/python/rust test defaults carry a defaulted placeholder ({target:./...}), so scoping works with no config edit and omitting the target still runs everything. Restricted to one shell-safe argument ([A-Za-z0-9._/:@-]); refused if the stored command has no {target}."New value: +"Optional target substituted for a {target} token in the stored command (e.g. a single test name or package). The shipped go/python/rust test defaults carry a defaulted placeholder ({target:./...}), so scoping works with no config edit and omitting the target still runs everything. Restricted to one shell-safe argument ([A-Za-z0-9._/:@-]); refused if the command has no {target} slot."
  2. Changed2 schema fields changedv0.17.2
    • changedInput schema / properties / slot / description
      Previous value: -"Which stored task command to run: build, lint, test, e2e (integration), or verify (build then test). The command is configured per language in [tasks.<lang>] and resolved for this workspace's language — you cannot pass an arbitrary command."New value: +"Which stored task command to run: build, lint, test, e2e, verify, or a project-defined slot under [tasks.<lang>]. session_start lists what's configured; an unconfigured slot is refused with that list."
    • removedInput schema / properties / slot / enum
      Removed value: -[
-  "build",
-  "lint",
-  "test",
-  "e2e",
-  "verify"
-]
  3. Changed1 schema field changedv0.17.0
    • changedInput schema / properties / target / description
      Previous value: -"Optional target substituted for a literal {target} token in the stored command (e.g. a single test name or package). Restricted to one shell-safe argument ([A-Za-z0-9._/:@-]); refused if the stored command has no {target}."New value: +"Optional target substituted for a {target} token in the stored command (e.g. a single test name or package). The shipped go/python/rust test defaults carry a defaulted placeholder ({target:./...}), so scoping works with no config edit and omitting the target still runs everything. Restricted to one shell-safe argument ([A-Za-z0-9._/:@-]); refused if the stored command has no {target}."
  4. First observedv0.16.6

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and is unusually transparent: it discloses trust requirements for project configs, cwd behavior, command provenance, target restrictions, and bounded output/runtime. This gives the agent accurate call-time expectations.

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?

Every sentence adds a distinct non-obvious fact: what is run, trust requirements, cwd, target semantics, and pairing with topology_affected. The core purpose is front-loaded, and the density is justified by the tool's complexity.

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?

For a side-effecting task runner with no annotations or output schema, the description covers the critical prerequisites: trust, working directory, no arbitrary shell, bounded execution, and relationship to topology_affected. The only notable omission is a precise statement of what the tool returns on success/failure, though 'output and runtime are bounded' gestures at it.

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%, and both slot and target already have detailed descriptions including allowed values, placeholder semantics, regex restriction, and refusal behavior. The prose description restates this information without adding materially new parameter meaning, so the baseline of 3 is appropriate.

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 first sentence identifies a specific action ('Run a stored per-language task command') and a concrete resource ([tasks.<lang>] slots), enumerating build/lint/test/e2e/verify. The explicit contrast 'no shell, no agent-supplied command line' separates it from arbitrary command runners like run_command without ambiguity.

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?

It clearly states when run_task applies (stored, per-language task slots; paired with topology_affected for which tests to run) and when it does not (no agent-supplied shell command, project configs must be trusted first). It stops short of naming run_command as the alternative for arbitrary commands, but the exclusion is clear enough.

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/plumbkit/plumb'

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