Skip to main content
Glama
sql-mcp
by ohankay

delete_job_step

Destructive

Deletes a specific SQL Server Agent job step using the job name and step ID, helping remove unwanted steps from a job.

Instructions

Delete one job step (step_id from get_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>",
      "step_id": "<step_id>"
    },
    "name": "delete_job_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
step_idYes
job_nameYes
connectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds the scope of deleting exactly one step and points to get_job for the step_id, but it does not elaborate on irreversibility, cascading effects, or permissions.

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?

The definition is one short sentence, front-loads the action and resource, and contains no filler. The parenthetical prerequisite is compact and useful.

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 simple destructive tool whose annotations already signal danger, the description is minimally viable: it names the operation and the step_id source. However, it leaves job_name and connection semantics unaddressed and gives no additional behavioral context for a destructive operation.

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%, so the description must compensate. It only clarifies where step_id comes from and leaves job_name and the optional connection parameter unexplained, meaning two of three parameters receive no meaningful semantic guidance.

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 description states a specific verb and resource: 'Delete one job step.' This clearly distinguishes it from sibling operations such as add_job_step, update_job_step, and delete_job, and it scopes the action to a single step.

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?

The parenthetical '(step_id from get_job)' gives a useful prerequisite for obtaining the step ID, but the description does not explicitly say when to use this instead of adjacent tools like delete_job or update_job_step, nor does it state when not to use it.

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