Skip to main content
Glama
sql-mcp
by ohankay

start_job

Starts a SQL Server Agent job asynchronously, optionally from a specified step; monitor progress and history with companion tools.

Instructions

Start a job asynchronously (optionally from a given step). Check progress with list_running_jobs / get_job_history.

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": "start_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_nameYes
step_nameNo
connectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly=false, idempotent=false, and non-destructive, so the safety profile is covered; the description's real contribution is disclosing that execution is asynchronous. It does not say what is returned to identify/track the launched job, nor what happens if the job is already running or the step name is invalid.

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?

Two compact sentences, front-loaded with the core action and followed by the follow-up pointer. No filler or redundant restatement of the name.

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

Completeness3/5

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

For a three-parameter starter tool with no output schema and zero schema coverage, the description covers the action and one parameter but leaves connection undefined and doesn't describe the return value or handle the caller needs to track progress.

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 three parameters, so the description must carry the load. It explains step_name reasonably ("optionally from a given step") and implies job_name, but the 'connection' parameter is never mentioned at all, leaving a required input ambiguous in purpose.

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 pairs a specific verb with a specific resource ("Start a job") and adds the async qualifier plus an optional starting point, so an agent can distinguish it from stop_job, create_job, or list_running_jobs. It stops short of explicitly naming a sibling it is not.

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 states the entry condition (launch a job, optionally from a named step) and routes the agent to list_running_jobs / get_job_history for follow-up, which is actionable guidance. It lacks any when-not guidance, e.g. how this differs from running a scheduled job.

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