Skip to main content
Glama
sql-mcp
by ohankay

delete_job

Destructive

Deletes a SQL Server Agent job and, by default, its history to clean up scheduled jobs managed through sql-mcp.

Instructions

Delete an Agent job (and by default its 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": "delete_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_nameYes
connectionNo
delete_historyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already flag this as destructive and non-idempotent, so the description's job is to say what is destroyed — and it does, disclosing that job history is removed by default. It stops short of stating irreversibility or that delete_history=false preserves the history, which would complete the picture.

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?

A single short sentence with the destructive scope front-loaded and zero filler. Nothing is padded or repeated from the schema.

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 destructive mutation tool with three undocumented parameters and no output schema, the description is too thin — it omits the effect of delete_history=false, what happens to related steps/schedules, and the failure behavior for a nonexistent job.

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 carries the full burden, yet it only implicitly gestures at delete_history via 'by default its history'. job_name and connection receive no explanation of format, expected connection context, or behavior when connection is null.

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?

States a specific verb and resource ('Delete an Agent job') and adds a scope qualifier about history removal, so the action is unambiguous. It does not name or contrast with nearby siblings such as delete_job_schedule or delete_job_step, so an agent must infer the distinction from the resource name alone.

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 when-to-use guidance, no prerequisite or permission note, and no mention of when to prefer a narrower delete (step/schedule) instead. The only implied guidance is the default history behavior.

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