Skip to main content
Glama

Rokha

by ai.rokha
OverviewDiscussionsAdmin

Trace Get

trace_get
Read-onlyIdempotent

READ one trace in full (input, result, status, timing) by id, or a whole run by run_id (status, steps with their trace ids, output, every trace). Signed in (Authorization: Bearer ): your own traces. No token: a PUBLIC rig's run is readable by anyone holding its trace id or run id — the runner's identity is stripped. Anything else answers not-found. REST twins: GET /api/traces/ · GET /api/rigs/runs/<run_id>.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoA trace UUID (every trace row shows it).
run_idNoA run UUID — the id rig_run / POST /api/rigs/run hand back. Pass this OR id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"UUID of the trace (the id shown on every trace row)"New value: +"A trace UUID (every trace row shows it)."
    • changedInput schema / properties / run_id / description
      Previous value: -"UUID of a whole run — every trace it wrote. Pass this OR id."New value: +"A run UUID — the id rig_run / POST /api/rigs/run hand back. Pass this OR id."
    • removedInput schema / properties / wallet_address
      Removed value: -{
-  "description": "Wallet address that owns the trace",
-  "type": "string"
-}
    • removedInput schema / required
      Removed value: -[
-  "wallet_address"
-]
  2. Changed3 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"UUID of the trace"New value: +"UUID of the trace (the id shown on every trace row)"
    • addedInput schema / properties / run_id
      Added value: +{
+  "description": "UUID of a whole run — every trace it wrote. Pass this OR id.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "wallet_address",
-  "id"
-]New value: +[
+  "wallet_address"
+]
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds substantially more: the auth requirement, the public-rig read path, the stripping of runner identity, and the not-found fallback. This is behavior an agent cannot infer from the structured fields.

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?

Dense and front-loaded with the core verb first, then modes, auth, and REST twins. The run-on sentence structure and stray whitespace make it slightly heavy, but nearly every clause carries load.

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?

With no output schema, the description carries the return-value burden and does so for both modes. Auth edge cases and failure semantics are also covered, leaving nothing an agent needs to call this 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?

Schema coverage is 100%, so the baseline is 3, but the description adds the return-shape distinction per parameter — id yields a single full trace while run_id yields a whole run with status, steps, trace ids and output. That is meaning beyond the schema's bare UUID descriptions.

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?

States a specific verb and resource ('READ one trace in full') and immediately covers the alternate mode (a whole run by run_id). It enumerates the returned fields for each mode, so an agent knows exactly what it gets.

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?

Explicitly explains when to pass id vs run_id, and lays out the auth decision tree (signed in = own traces, no token = public rig runs, otherwise not-found). It does not route to the trace_search sibling for finding traces in the first place, which is the one remaining gap.

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

All Rokha toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources