Skip to main content
Glama

Job Result

job_result
Read-only

Fetch an async job's outcome, including status, elapsed time, and result or error. Use discard to free a completed job and its cache entry.

Instructions

Fetch an async job's outcome. Returns {job_id, kind, status, elapsed_s, result (when done) | error (when failed)}; while running neither is set. discard=True frees a terminal job (and its cache entry) once you have 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": "job_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
discardNo
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.1/5.0
Behavior1/5

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

The description states that discard=True frees a terminal job and its cache entry, which is a state mutation. This contradicts the readOnlyHint=true annotation, which promises the tool does not modify its environment. No destructiveHint is present to reconcile the cleanup behavior.

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?

The description is front-loaded and compact, with no wasted sentences. The return-shape sentence is dense but useful, and the discard caveat is placed at the end where it belongs.

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?

There is no output schema, so the description carries the burden of explaining returns, which it does by listing job_id, kind, status, elapsed_s, and result/error conditions. It also explains discard cleanup. The main gap is that it does not address the annotation contradiction or job lifecycle details more explicitly.

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 only 33%, with workspace documented in the schema. The description adds useful meaning for discard=True and explains the return fields, but job_id is left implicit and workspace is only covered by the schema. It partially compensates for the low coverage.

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 states a specific verb and resource: fetching an async job's outcome. It also outlines the return shape, so the tool's purpose is clear. It does not explicitly distinguish itself from siblings like job_status or job_list.

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?

It implies polling behavior by noting that while running neither result nor error is set, and it says discard should be used once a terminal job is in hand. However, it does not explicitly say when to use this instead of job_status or job_list, nor does it name alternatives.

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