Skip to main content
Glama
sql-mcp
by ohankay

delete_job_schedule

Destructive

Detach a schedule from a SQL Agent job and delete the schedule when no other job uses it.

Instructions

Detach a schedule from a job (and delete it if no other job uses it).

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>",
      "schedule_name": "<schedule_name>"
    },
    "name": "delete_job_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_nameYes
connectionNo
schedule_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description earns credit for disclosing a genuinely non-obvious behavior beyond the annotations: the schedule is only deleted if no other job references it, which tells the agent the blast radius may be smaller than a plain delete. It does not say what happens when the pairing does not exist or whether errors are raised or silently ignored.

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 well-formed sentence with the destructive conditional front-loaded in parentheses. No filler, no restatement of the tool name, and nothing that could be trimmed without losing meaning.

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 destructive, non-idempotent mutation with three undocumented parameters and no output schema, one sentence leaves real gaps: the role of 'connection', error/not-found behavior, and whether the operation is reversible are all absent. The orphan-deletion caveat is the single most important thing to convey, and it is conveyed, which keeps this at minimum-viable rather than inadequate.

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 of explaining the three parameters, and it explains none of them. job_name and schedule_name are guessable from their names, but the optional 'connection' parameter is entirely unexplained in both the schema and the description, leaving an agent to guess whether it scopes the operation or is unrelated.

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?

Uses a specific verb ('Detach') plus the resource ('a schedule from a job') and adds the conditional side effect that the schedule itself is deleted when orphaned. An agent can distinguish this from add_job_schedule by the verb alone. It stops short of naming the counterpart tool for re-attaching a schedule, so it is not a full 5.

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 detach framing implies when to use it (removing a schedule binding from a specific job), but there is no explicit statement of preconditions such as whether the schedule must currently be attached to the job, nor any pointer to add_job_schedule for the inverse operation. Usage is inferable rather than stated.

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