Skip to main content
Glama
sql-mcp
by ohankay

add_job_schedule

Attach a new schedule to an existing SQL Agent job so it runs at defined times; use the same schedule fields as job creation.

Instructions

Attach a new schedule to a job. Same schedule fields as create_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>",
      "schedule": "<schedule>"
    },
    "name": "add_job_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_nameYes
scheduleYes
connectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare this a non-read-only, non-destructive, non-idempotent mutation, so the safety bar is partly covered. The description adds nothing about what happens when a schedule already exists (non-idempotent, so duplicates are possible), required permissions, or error behavior — meaningful gaps for a mutation with no output schema.

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?

Two short sentences, front-loaded with the operation and followed by the one non-obvious hint. Nothing is wasted, though the second sentence is terse to the point of being cryptic.

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?

A non-idempotent mutation with a nested object parameter, zero schema coverage and no output schema needs far more than two sentences. An agent could not determine required permissions, duplicate-handling, or what the schedule object's fields and defaults look like without opening create_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% across three parameters, including a nested free-form schedule object, so the description must carry the semantics. "Same schedule fields as create_job" is a genuinely useful cross-reference, but it forces the agent to consult another tool and job_name and connection get no mention at all.

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?

"Attach a new schedule to a job" gives a specific verb (attach) and resource (schedule) and distinguishes this from create_job. It is not fully clear what a schedule object contains, but the direction of the operation is unambiguous.

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?

The description never states when to use this versus create_job, update_job, or delete_job_schedule. The pointer to create_job implies you must first have a job, but no exclusions or prerequisites are spelled out.

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