Skip to main content
Glama

Get a job

job_get
Read-onlyIdempotent

Read one job whole: its purpose, its description (workspace_load may cut long ones: descriptionCut), its task definitions with every step's role, cadence, instructions, approval, latest check (who and when) and health (on_time, late, not_checked, no_schedule), the job's health (on_schedule, late, not_checked or no_schedule, from its steps), its agents with their roles and when each was last seen, whether it is archived, its revision for job_update, its newest outputs (what went out under it; outputsCut when large ones were left out: output_list job= reads them all) and outputCounts by status. workspace_load lists the workspace's jobs. A job you cannot read is UNAVAILABLE.

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": {
      "id": "<id>"
    },
    "name": "job_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe job, by its id (job_create returns it; workspace_load lists your jobs and the others by id).

Output Schema

NameRequiredDescriptionDefault
jobYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: truncation semantics (descriptionCut, outputsCut), the UNAVAILABLE failure state, and the enumerated health values (on_time, late, not_checked, no_schedule). It does not discuss permissions or access scoping, 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.

Conciseness3/5

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

The lead clause "Read one job whole" is well front-loaded, but the remainder is one very long run-on sentence with heavy parenthetical nesting that is hard to parse. The content is largely earned, but the structure could be broken into shorter statements for readability.

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?

An output schema exists, so return values need not be explained, yet the description still usefully flags truncation and the UNAVAILABLE state that an agent must handle. For a single-parameter read tool this is close to complete; only access/permission expectations 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 coverage is 100% and the single id parameter is fully documented in the schema, including where to obtain it. The description adds no format or sourcing detail beyond what the schema already provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Read one job whole") and then enumerates exactly what is returned: description, task definitions, health, agents, revision, outputs. It is clearly distinguishable from workspace_load (lists jobs) and output_list (reads all outputs), both of which are named.

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?

Routes the agent to alternatives in two places: workspace_load for listing jobs and output_list for reading all outputs when outputsCut occurs, and implies the revision is fetched ahead of job_update. It does not explicitly state when-not to use it versus task_get for step-level detail, so it falls short of full when/when-not coverage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.