Skip to main content
Glama

colab_job_status

Read-only

Retrieves a specific Colab job by ID, returning its state, exit code, recent logs, and artifacts so you can monitor or debug remote compute work.

Instructions

Get one of this client's Colab jobs, including its state, exit code, log tails, and artifacts.

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": {
      "jobId": "<jobId>"
    },
    "name": "colab_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint=true annotation already establishes this is a safe, non-mutating read, so the description is not carrying the safety burden. It does add useful payload context by listing state, exit code, log tails, and artifacts, but says nothing about whether the call blocks, how fresh the status is, or how log tails are truncated.

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?

One front-loaded sentence with no filler, and the payload enumeration earns its place. It could be marginally tighter by naming the identifier it operates on rather than the generic 'Get'.

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?

For a one-parameter read-only tool this is close to adequate, and the description usefully substitutes for the absent output schema by naming the returned fields. It leaves gaps on how to obtain a jobId and on terminal vs. in-progress states, which matter for a polling tool.

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 description must compensate; it only implies that the single jobId parameter scopes to 'this client's' jobs, without saying where the id comes from (e.g., returned by colab_run_job) or what happens for an unknown or foreign id. The uuid format and pattern in the schema still carry the type-level meaning.

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 specific verb ('Get') and resource ('one of this client's Colab jobs'), and enumerates the payload (state, exit code, log tails, artifacts), which separates it from the pool-oriented siblings. It stops short of explicitly naming how it differs from colab_pool_status or colab_run_job, so it is clear but not fully differentiated.

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 or when-not-to-use guidance, and no mention of the natural workflow (polling after colab_run_job, or before colab_cancel_job). An agent must infer the polling context from the tool name alone.

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