EMT Compute

emt_training_events

Read-onlyIdempotent

Read up to 100 training events with metrics, runtime and observed dataset hashes when recorded. For full history start after=0 and latest=false, then repeat with the greatest returned seq until an empty page. latest=true returns the most recent window only. Visible devices are not proof of GPU utilization.

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": "<job>"
    },
    "name": "emt_training_events"
  }
}

Input Schema

Name	Required	Description
`job`	Yes	UUID of a job owned by the API key's workspace.
`after`	No	Return events with seq greater than this value (0 = from the start).
`latest`	No	true returns only the most recent window of events instead of paging from after.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 7, 2026

addedInput schema / properties / after / description

Added value: +"Return events with seq greater than this value (0 = from the start)."

addedInput schema / properties / job / description

Added value: +"UUID of a job owned by the API key's workspace."

addedInput schema / properties / latest / description

Added value: +"true returns only the most recent window of events instead of paging from after."

AddedNov 5, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations, it discloses the 100-event cap, how to page through full history, how latest=true differs, and that dataset hashes may only be present when recorded. The warning that visible devices are not proof of GPU utilization adds important interpretive context for the returned metrics.

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?

The description is compact and front-loaded: purpose first, paging workflow second, latest behavior third, and a domain caveat last. Every sentence contributes useful information without repetition.

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?

For a read-only, three-parameter event-listing tool with rich annotations and no output schema, the description covers the page size, returned data categories, paging procedure, latest-window behavior, and a key caveat about interpretation. An agent has enough information to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents all three parameters at full coverage, but the description adds meaningful interaction semantics: after=0 plus latest=false starts a full-history walk, the greatest returned seq should be used for the next call, and latest=true selects only the recent window.

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 gives a specific verb and resource: it reads training events and names the returned content such as metrics, runtime, and observed dataset hashes. It is clearly distinct from job-oriented siblings by focusing on events, but it does not explicitly name or contrast an alternative sibling tool.

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 description gives clear operational guidance for full-history paging versus retrieving only the most recent window via latest=true. It does not explicitly state when not to use this tool or name a preferred sibling for related job-level queries.

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

All EMT Compute tools Inspect

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

Need Help?