Skip to main content
Glama

codebuddy_stop_job

Stop a running CodeBuddy background job by supplying its job ID, allowing you to halt stalled or unwanted tasks and free up processing resources.

Instructions

Stop a running CodeBuddy background job.

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": {
      "jobId": "<jobId>"
    },
    "name": "codebuddy_stop_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, yet it says nothing about whether stopping is irreversible, what happens to job output or partial work, whether it blocks until termination, or what error surfaces for an unknown/already-stopped jobId. 'Stop' implies mutation and likely destruction of in-flight work, but that is left for the agent to guess.

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 short sentence with the action front-loaded and no filler. It is efficient, though the terseness borders on under-specification given what is omitted.

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?

Although the tool is simple (one required parameter, no output schema), a terminate-style mutation tool with zero annotation coverage needs at least the source of jobId and the effect/irreversibility of the stop. Neither is present, so an agent cannot confidently call it without trial and error.

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% and the single jobId parameter has only a minLength constraint, so the description needed to explain where the ID comes from (e.g., returned by the start tool) and its expected form. It adds nothing beyond the schema.

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 description uses a specific verb and resource ('Stop a running ... background job'), so the agent can tell it terminates an existing job rather than starting or inspecting one. It does not name or distinguish itself from siblings such as codebuddy_job_status or codebuddy_start_development, which keeps it out of 5 territory.

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

Usage Guidelines2/5

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

There is no guidance on when to stop versus let a job finish, no mention of prerequisites (e.g., the job must be running), and no reference to alternatives like checking status first. Usage is only implied by the word 'running'.

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