Skip to main content
Glama
sql-mcp
by ohankay

update_job_step

Modify SQL Server Agent job step fields such as name, command, database, subsystem, success/failure actions, and retries by specifying the job, step ID, and changes.

Instructions

Change fields of a job step (name, command, database, subsystem, on_success, on_fail, retries, ...).

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>",
      "changes": "<changes>"
    },
    "name": "update_job_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
changesYes
step_idYes
job_nameYes
connectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety profile is covered, but the description adds nothing beyond that. It never says whether 'changes' merges into existing fields or replaces them, whether omitted fields are preserved, what happens if the step doesn't exist, or what an idempotentHint=false implies for retries.

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 front-loaded sentence with no filler; the parenthetical field list is efficient. The trailing ellipsis slightly undercuts precision but avoids bloat.

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 mutation tool with a nested free-form object and no output schema, the definition covers the basic purpose but omits merge semantics, connection scoping, and failure behavior. An agent could call it, but would be guessing about how 'changes' is applied.

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 coverage is 0% and 'changes' is an opaque object with additionalProperties=true, so the description's field enumeration (name, command, database, subsystem, on_success, on_fail, retries, ...) does add real value. However it leaves the list open-ended and says nothing about the three top-level parameters (job_name, step_id, connection) or their formats.

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 states a specific verb and resource ('Change fields of a job step') and enumerates the mutable fields, which lets an agent tell it apart from update_job and add_job_step without opening the schema. It stops short of explicitly naming those siblings.

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 an implied condition that the step must already exist, but no explicit when-to-use guidance, no alternative named (e.g., add_job_step for new steps, update_job for job-level fields), and no mention of prerequisites such as owning the job or a required connection.

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