Skip to main content
Glama

run_job

Destructive

Execute approved deterministic workspace workflows—Git status/diff summaries, Python compilation, or tests—after allow_jobs is enabled.

Instructions

Execute a locally approved, deterministic workspace workflow; requires allow_jobs

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "recipe": "<recipe>",
      "workspace": "<workspace>"
    },
    "name": "run_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
recipeYes
workspaceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=false, so the safety posture is structured data. The description adds real context beyond that: the workflows are deterministic and locally approved, and the caller must hold the allow_jobs capability. It does not explain what the destruction consists of (files written? repo state touched?) or how output differs per recipe.

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?

A single front-loaded clause with zero filler, and the permission requirement is appended at the end where it is easy to spot. It is perhaps terse to the point of under-specification rather than bloated.

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

Completeness2/5

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

This is a destructive, permission-gated execution tool with an undocumented free-text parameter and no output schema, so the description should do much more work than one sentence. An agent cannot tell what each recipe does, what the tool returns, or what side effects workspace-scoped execution produces.

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

Parameters2/5

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

Schema description coverage is 0% for two required parameters, so the description carries the full burden and adds nothing: neither the recipe enum values nor the meaning/format of workspace (path? name? absolute?) is explained. The enum is partially self-describing, but workspace is entirely opaque.

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?

"Execute a ... deterministic workspace workflow" gives a specific verb and resource, and "deterministic" distinguishes it from the raw-command sibling run_command. It stops short of naming the alternatives or the fixed recipe set, so the differentiation is inferable rather than stated.

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

Usage Guidelines3/5

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

"requires allow_jobs" flags a prerequisite gate and "locally approved" hints at the approval context, which is useful. But there is no explicit when-to-use versus run_command, no statement of which tasks map to which recipe, and no exclusion for cases where an arbitrary command is needed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.