Skip to main content
Glama

get_job

Read-only

Check the status, progress, elapsed time, and final result of a background job from a long-running ServiceNow tool; optionally wait for it to complete.

Instructions

Check a background job started by a long-running tool (async: true, or a call that ran past about 20 seconds). Returns status (running, completed, failed, cancelled), progress, elapsed time and, once finished, the tool result. Pass wait_seconds to wait for it to finish.

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_id": "<job_id>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job_id a long-running tool returned
wait_secondsNoWait up to this many seconds (max 25) for the job to finish before answering. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds real value on top: the four possible status values (running, completed, failed, cancelled), the fields returned (progress, elapsed time, tool result), and the fact that the result only appears once finished. It omits retention/expiry of job records and polling etiquette, keeping it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what the tool does and the return shape, followed by the one actionable parameter tip. The parenthetical defining 'long-running tool' earns its place by making the trigger condition unambiguous.

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?

With no output schema, the description carries the return-value burden and does so by enumerating statuses and the result fields. For a two-parameter read tool it is nearly complete; only job lifetime/retention behavior and what an empty progress means are unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are already documented in the schema, and the description largely restates them. It does add the purpose-level framing of wait_seconds as a blocking wait for completion, but contributes no new syntax, format, or edge-case detail beyond the schema's 'max 25'.

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 concrete verb and resource (check a background job) and scopes it tightly to jobs 'started by a long-running tool (async: true, or a call that ran past about 20 seconds)', which separates it conceptually from scheduled-job siblings like get_scheduled_job. It stops short of naming any sibling explicitly, so the differentiation must be inferred from the origin clause.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear triggering condition: call this after a long-running tool returns a job or a call exceeded ~20 seconds. It also explains the wait_seconds choice (block until finished vs. return immediately). It does not say when to prefer this over get_pa_job or advise against tight polling, leaving some operational guidance unstated.

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

Deploy Server

Other Tools