Skip to main content
Glama
sql-mcp
by ohankay

get_job

Read-onlyIdempotent

Retrieves SQL Agent job details, including properties, steps with commands, and schedules, by job name and optional connection.

Instructions

Job details: properties, steps (with commands) and schedules.

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": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_nameYes
connectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that returned details include properties, steps with commands, and schedules, but it does not mention error behavior, connection scoping, or what happens when a job is absent.

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?

The description is a single front-loaded fragment with no wasted words. It is efficient, though its terseness leaves important details unstated.

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?

With no output schema, the description reasonably enumerates the returned content areas. However, it does not explain the required job_name or optional connection parameter, and it lacks any note about connection selection or failure modes, which matters for a zero-coverage schema.

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 must compensate for two undocumented parameters. It does not explain job_name beyond the obvious job reference, and it says nothing about the optional connection parameter or how it affects lookup.

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 clearly identifies the resource and scope: job details covering properties, steps with commands, and schedules. It is more specific than a tautology, but it does not distinguish this tool from siblings such as list_jobs or get_job_history.

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 explicit guidance on when to call get_job versus list_jobs or get_job_history. Usage is implied by the tool name and description, but alternatives and exclusions are not addressed.

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