Skip to main content
Glama
sql-mcp
by ohankay

stop_job

Stops a running SQL Agent job by job name, with optional connection targeting, to halt execution and prevent further job activity.

Instructions

Stop a running 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": {
      "job_name": "<job_name>"
    },
    "name": "stop_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_nameYes
connectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the mutation profile is mostly covered. The description adds only the precondition that the job is running; it does not say whether the stop is graceful or forceful, whether it can be undone, or how the caller learns the job actually stopped. With annotations doing the heavy lifting, a 3 is appropriate.

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 no wasted words and the purpose front-loaded. It is concise, though its brevity reflects under-specification rather than efficiency.

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?

For a mutation tool with zero schema description coverage, an undocumented second parameter, and no output schema, the description does too little. It omits the 'running' prerequisite enforcement, whether stopping is graceful, and what happens if the job is already stopped.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must compensate entirely, and it does not. 'job_name' is self-evident, but 'connection' (nullable, defaulting to null) is undocumented in both the schema and the description; an agent cannot tell which connection context is used or whether the job name is globally unique.

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

Purpose3/5

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

The description gives a specific verb and resource ('Stop a running job'), which is clearer than a tautology. However, it does not distinguish this from siblings like kill_session, list_running_jobs, delete_job, or start_job, nor does it specify scope (single job vs. all jobs).

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 use this versus alternatives such as delete_job or kill_session, both of which could plausibly terminate work. The only implied context is that the job must currently be running.

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