Skip to main content
Glama
sql-mcp
by ohankay

list_jobs

Read-onlyIdempotent

Retrieve SQL Server Agent jobs with filters for enabled status and name, including running state, last outcome, and next run time to monitor job health and schedules.

Instructions

List SQL Server Agent jobs with enabled flag, running state, last outcome and next run time.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledNo
name_likeNo
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, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the return-field set, which is useful, but says nothing about pagination, result volume, or whether connection defaults to a local instance.

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 resource comes first and the payload fields follow. It is efficient, though it spends its words on outputs rather than the filters an agent must supply.

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 usefully covers what is returned. However, for a three-parameter tool with zero schema coverage and several close siblings, it leaves the caller without enough information to construct a correct, well-targeted call.

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 (enabled, name_like, connection), and the description does not explain any of them. The word "enabled" appears only as a returned field, which may even mislead an agent into thinking it describes the filter semantics; name_like's matching behavior and connection's format are entirely undocumented.

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?

States a specific verb and resource ("List SQL Server Agent jobs") and enumerates the returned attributes (enabled flag, running state, last outcome, next run time). It does not distinguish itself from siblings such as list_running_jobs or get_job, so an agent must infer the difference from names alone.

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 tool, when to prefer list_running_jobs or get_job, or what prerequisites exist. The listing intent is implied by the verb, but no guidance or exclusion is given.

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