Skip to main content
Glama

devtune_get_agent_picks_run_trace

Read-onlyIdempotent

Read one page of a project-owned Agent Picks run's console trace: redacted prompt, setup, narration, tool calls and results, file edits and errors, ordered by attempt then seq. An attempt's lines are available once that attempt finishes; a running attempt has none yet, and an attempt whose transcript could not be read has one error line, Trace unavailable for this attempt. availability is stored, pending (none yet: the run is running or finished within the last hour) or not_retained (none expected: it finished over an hour ago, as every run before traces were kept did), and attempts marks each attempt stored or not. A model_call item follows the first line of its attempt carrying its provider response id, else a tool-call id, with tokens, cost and the running total of placed calls. Calls that match no line are in unplaced with a reason (failed, no_ids, pending or unmatched), 200 at a time: the first page (cursor 0, 0) carries the first 200, and passing unplaced_pagination.after_id as after_unplaced returns the next 200; Codex reports no ids, so its calls are never placed. totals counts every proxy call. Each line carries preview, its first 65,536 characters, with preview_truncated when the stored text is longer; to read one line's whole stored text (up to 1 MiB, detail.truncated beyond), pass after_attempt, after_seq one before the line, limit 1 and full true. Pass pagination.after_attempt and after_seq back until has_more is false. limit defaults to 50, maximum 100; a page also stops after 256 KiB of lines. Requires Agent Picks and visibility.read. Cannot change a run.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullNo
limitNo
run_idYes
after_seqNo
after_attemptNo
after_unplacedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it explains availability states (stored/pending/not_retained), why a running attempt has no lines, the single 'Trace unavailable' error line, how calls become 'unplaced' with reasons, preview truncation at 65,536 chars, the 256 KiB page cap, and the Agent Picks + visibility.read requirement. Declares 'Cannot change a run', consistent with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, which helps, but the body is one dense, run-on block that is hard to parse and repeats pagination concepts. Information density is high but structural clarity is poor for a description this long.

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 6-parameter, paginated, no-output-schema read tool, the description covers return shape (lines, unplaced, totals, model_call items), ordering, pagination termination, availability, and permissions. An agent has everything needed to call and page 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?

With 0% schema description coverage the description carries the load and largely does: it defines limit (default 50, max 100), full, after_attempt/after_seq, and after_unplaced roles. Minor weakness is the confusing phrasing 'passing unplaced_pagination.after_id as after_unplaced', which introduces a name not present in the schema.

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?

Opens with a specific verb and resource: 'Read one page of a project-owned Agent Picks run's console trace', and enumerates exactly what the trace contains (prompt, setup, narration, tool calls, edits, errors). The scope is precise enough to separate it from run/summary siblings, though it never explicitly names an alternative tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives strong operational guidance (pagination via pagination.after_attempt/after_seq until has_more is false, 200-at-a-time unplaced reads) but never states when to reach for this tool versus devtune_get_agent_picks_run or devtune_list_agent_picks_runs. Usage is implied by the trace resource rather than contrasted against siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources