Skip to main content
Glama

Get job

get_job
Read-onlyIdempotent

Inspect an authorized scientific job, its bounded ordered events and its linked run's inputs and output manifest. Reports partial context explicitly. Reading a job never cancels or restarts it.

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
limitNo
job_idYes
after_sequenceNo

Output Schema

NameRequiredDescriptionDefault
jobYes
relatedYes
warningsYes
context_completeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real value by promising that partial context is reported explicitly and that reading never cancels or restarts a job — a genuine behavioral guarantee not in the annotations. It does not disclose pagination/ordering semantics for the events beyond 'bounded ordered', nor authorization-failure behavior.

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?

Three short sentences, each carrying distinct information: what is returned, how partial results are handled, and the non-destructive guarantee. Front-loaded with the resource scope and free of filler.

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 an output schema present, return-value explanation is not required, and the annotations carry the safety profile. Still, for a tool with a paging cursor whose meaning is undocumented, plus an authorization precondition that is only alluded to, an agent could call it correctly but might mishandle event pagination or misread a partial result.

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 0%, so the schema gives only names, types, defaults and bounds (limit 1-50 default 20, after_sequence, job_id). The description's 'bounded ordered events' implies that limit and after_sequence constrain and page the event list, which is meaningful added context, but it never explains what after_sequence means (exclusive cursor? sequence number?) or whether limit applies to events only. Meaningful but incomplete compensation for a 0% coverage schema.

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 uses a specific verb ('Inspect') and names the resource precisely: a job, its bounded ordered events, and the linked run's inputs and output manifest. That is far more informative than the title 'Get job' and separates it from siblings like cancel_job or get_artifact. It stops short of explicitly naming an alternative, but the scope is unmistakable.

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 'authorized scientific job' implies a prerequisite (the job must be visible to the caller) and the closing sentence hints at the safe-read use case versus cancel_job. However, there is no explicit when-to-use or when-not-to-use statement, no pointer to the sibling that mutates jobs, and no guidance on when to page events versus fetch the job alone.

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.

Resources