Skip to main content
Glama
sql-mcp
by ohankay

get_job_history

Read-onlyIdempotent

Retrieve recent SQL Agent job and step execution history, including status, duration, and messages, with filters for job name, connection, and failed runs.

Instructions

Recent job/step executions with status, duration and messages (newest first).

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

Input Schema

NameRequiredDescriptionDefault
topNo
job_nameNo
connectionNo
failed_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/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. The description adds useful context beyond that — result ordering (newest first) and the fields returned — but says nothing about how far back 'recent' reaches, whether results are capped by default, or whether filtering is server-side.

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 returned fields and ordering come first. It is efficient, though the extreme brevity contributes to the gaps elsewhere rather than earning its place through precision.

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?

With four undocumented parameters, no output schema, and no annotations explaining filtering semantics, one sentence is not enough. An agent cannot tell what 'top' defaults to mean, whether job_name is an exact or partial match, or how 'recent' is bounded.

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% and there are four parameters (top, job_name, connection, failed_only), none of which the description explains. Only 'recent' loosely hints at a limit, and 'failed_only' — a significant filtering behavior — is entirely undocumented outside its name.

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 resource (job/step executions) and states what comes back (status, duration, messages) plus ordering (newest first). It does not explicitly distinguish itself from siblings like list_jobs, get_job, or list_running_jobs, but the returned entity and contents are clear enough to identify the tool.

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 when-to-use guidance at all: nothing says to call this instead of list_jobs, get_job, or list_running_jobs, and no prerequisites are stated. The only implied usage cue is 'recent', which suggests historical rather than live data, but that is left to inference.

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