Skip to main content
Glama
sql-mcp
by ohankay

update_job

Modify SQL Agent job settings such as name, enabled state, description, category, owner, connection, or start step to keep job configuration current.

Instructions

Rename / enable / disable / change description, category, owner or start step of a 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>"
    },
    "name": "update_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledNo
categoryNo
job_nameYes
new_nameNo
connectionNo
descriptionNo
owner_loginNo
start_step_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare this is a non-read-only, non-idempotent, non-destructive, closed-world mutation, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say whether unspecified fields are left untouched, what happens to a running job when disabled, or what permissions are needed.

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 dense sentence that front-loads the verbs and lists the mutable fields without filler. It is efficient, though the slash-delimited list is terse enough to be slightly ambiguous about which field each verb maps to.

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 an 8-parameter mutation tool with zero schema coverage, no output schema, and no behavioral notes, one sentence is not enough. The agent lacks the partial-update semantics, the identity-vs-rename distinction, and any indication of side effects or required permissions.

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?

Schema description coverage is 0% across 8 parameters, so the description carries the burden and it only partially does so. It maps most fields to actions (rename implies new_name, enable/disable implies enabled, start step implies start_step_id), but it never distinguishes job_name from new_name, ignores the connection parameter entirely, and does not explain the null-default semantics that make this a partial update.

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 names a specific set of operations on a concrete resource: rename, enable/disable, and change description, category, owner, or start step of a job. An agent can identify this as the general job-mutation tool. It does not explicitly separate it from update_job_step or create_job, so it stops short of a 5.

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 statement of when to use this versus update_job_step, delete_job, or list_jobs, and no prerequisites or preconditions are given. The only guidance is the implied mapping from listed fields to actions, which the agent must infer.

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