Skip to main content
Glama
Sign In

Runcrate

by io.github.aeonmindai
OverviewDiscussionsAdmin

List job outputs

list_job_artifacts
Read-onlyIdempotent

List the files a job kept: everything its command wrote under $RUNCRATE_OUTPUT_DIR (/workspace/outputs) is uploaded when the command ends, whatever its status, up to 5 GB and 1000 files, and kept 30 days. Returns [{ path, bytes, sha256 }]. read_job_artifact returns one. A job still running has none yet.

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

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

A4.5/5.0
Behavior5/5

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

Annotations only declare read-only/idempotent/non-destructive; the description adds substantive behavior the agent could not infer: uploads happen regardless of exit status, caps of 5 GB and 1000 files, 30-day retention, and the exact return shape [{ path, bytes, sha256 }]. These are the constraints that determine whether the agent's plan will succeed.

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?

Extremely dense with zero waste: scoping, limits, return shape, sibling pointer, and the running-job caveat, with the core purpose front-loaded. Every clause conveys a fact the agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Though there is no output schema, the description supplies the return structure, size/count limits, retention, and the empty-result edge case, so nothing needed to call this correctly is missing.

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 100%, so id, workspace, and environment are already documented, and the description adds nothing about the workspace/environment scoping behavior. Baseline 3 applies since the schema carries the parameter burden.

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?

Opens with a specific verb and resource ('List the files a job kept') and explicitly distinguishes itself from the sibling that fetches a single artifact ('read_job_artifact returns one'). An agent can pick between the two without opening either schema.

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?

The alternative is named and the distinguishing condition is implied (many files vs one). It also adds a real usage caveat: a still-running job has no artifacts yet, so the agent knows an empty result is not an error. It stops short of explicitly saying 'call this first to discover paths, then read_job_artifact', so it falls just below the top score.

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