Skip to main content
Glama
sql-mcp
by ohankay

list_running_jobs

Read-onlyIdempotent

Retrieve currently executing SQL Agent jobs with elapsed time and current step to monitor active workloads and identify long-running or stalled tasks.

Instructions

Jobs currently executing, with elapsed time and current step.

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_running_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
connectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds useful return context — elapsed time and current step — but says nothing about ordering, size limits, or how the optional connection scopes results, and there is no output schema to fill that gap.

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 fragment with no filler, and the return fields are stated up front. It is arguably too terse for the scope it leaves unexplained, but nothing in it is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple, read-only, zero-required-parameter listing tool with full annotation coverage, the description supplies the essential scope plus the two return fields an agent would care about. The only real gap is the unexplained connection parameter, which the input schema also leaves undocumented.

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?

There is one parameter (connection) with 0% schema description coverage and a null default, and the description does not mention it at all — not what a connection identifies, nor what omitting it means (default connection? all connections?). With coverage this low the description needed to compensate and does not.

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+resource pair: listing jobs that are 'currently executing,' which scopes it to a filtered subset rather than all jobs. It never names list_jobs explicitly, so the distinction from the sibling is inferred from the word 'running' rather than stated.

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 phrase 'currently executing' implies the usage context (live monitoring) but there is no explicit statement of when to prefer this over list_jobs, get_job_history, or transaction_status, and no prerequisites or exclusions are given.

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