Skip to main content
Glama
sql-mcp
by ohankay

add_job_step

Add a step to an existing SQL Server Agent job, with the same step fields as job creation; set step_id to insert it at a specific position.

Instructions

Add a step to an existing job. Same step fields as create_job; set "step_id" to insert at a position.

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": "<step>"
    },
    "name": "add_job_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepYes
job_nameYes
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 establish readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is largely covered. The description adds useful context that step fields are shared with create_job and that step_id controls insertion position, but it does not warn that repeated calls with identical steps will duplicate (the non-idempotent behavior) or what happens when step_id is omitted.

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 short sentences with zero filler; the core operation is front-loaded and the field-reuse note follows immediately. Nothing in the text is redundant with the title or 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 non-idempotent mutation with an untyped nested step object, no output schema and three undocumented parameters, the description is thinner than ideal. It covers the step payload by cross-reference but omits connection, job_name scoping, and the duplicate-step consequence of repeated calls.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage and a nested, untyped step object (additionalProperties: true), the description carries the burden of explaining parameters. It compensates partially by pointing to create_job for valid step fields and by explaining step_id's insertion semantics, but leaves job_name and the connection parameter entirely unexplained.

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 ('Add a step to an existing job'), which is clearly separable from create_job, update_job_step and delete_job_step by name. It stops short of explicitly naming which sibling to use instead when the intent is to modify or reposition an existing step, so it is clear but not fully differentiated.

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 only conditional guidance given is 'set "step_id" to insert at a position', which describes a parameter mode rather than when to choose this tool over update_job_step or create_job. The choice to add a step rather than update or create is only implied by the verb.

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