Skip to main content
Glama
Sign In

Runcrate

by io.github.aeonmindai
OverviewDiscussionsAdmin

Get a job timeline

get_job_events
Read-onlyIdempotent

A job's timeline, oldest first: [{ at, kind, detail, attempt }]. Kinds: created, queued, launch_attempt, launch_failed, machine_up, driver_wait_start, driver_ready, code_fetch_start, code_fetch_end, image_pull_start, image_pull_end, started, exited, retrying, artifacts_uploaded, stopped. Use it to see where a job spent its time or why it failed before its command ran (no capacity, the GPU driver, the code or the image).

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": "get_job_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesJob ID
workspaceNoWorkspace ID (optional: defaults to the authenticated workspace)
environmentNoEnvironment name (optional: defaults to the environment this session acts in)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / env
      Removed value: -{
-  "description": "Environment name (optional — defaults to main)",
-  "type": "string"
-}
    • addedInput schema / properties / environment
      Added value: +{
+  "description": "Environment name (optional: defaults to the environment this session acts in)",
+  "type": "string"
+}
    • changedInput schema / properties / workspace / description
      Previous value: -"Workspace ID (optional — defaults to authenticated workspace)"New value: +"Workspace ID (optional: defaults to the authenticated workspace)"
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so safety is covered. The description goes further by disclosing the return payload shape, ordering, and the meaning of all sixteen event kinds, which is real value beyond the annotations; only truncation/pagination behavior is unstated.

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 payload shape and ordering are front-loaded, followed by the kind list and then the use case. The sixteen-item enumeration is long but each item is a distinct, useful diagnostic state, so it largely earns its space.

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 specifying the record fields and every kind. Together with the annotations, an agent has enough to call it and interpret results; only edge cases like very long timelines 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%, so the schema already explains id, workspace, and environment including their defaults. The description adds no additional parameter meaning, so the baseline of 3 applies.

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 the resource (a job's timeline) and its ordering ('oldest first'), plus the exact record shape and the full enumeration of event kinds. It implicitly separates itself from get_job/get_job_logs/get_job_metrics by framing the result as a phase-by-phase timeline with pre-command failure causes, though it never names a sibling directly.

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?

'Use it to see where a job spent its time or why it failed before its command ran (no capacity, the GPU driver, the code or the image)' gives a concrete when-to-use context and, via the parenthetical, hints that this is the right tool for launch-stage problems. No explicit exclusions or named alternatives are given.

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

All Runcrate toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources