Skip to main content
Glama

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Get Run Transcript

get_run_transcript
Read-only

Use this when a run's one-line summary isn't enough (e.g. "why did you skip person X in that run?"). Get a run's id from get_agent_details — each entry in its recent_runs list carries one; this returns the same message parts the web Activity tab renders for that run.

The transcript is paginated over its message parts — a heavy run records many. Page with offset while has_more is true. Dict with run_id, the run's summary message + details, status ('completed'/'failed'), created_at, total_messages (parts in the whole run), returned_messages (parts in this page), offset, has_more, and a messages array (role, content or tool_name/args, created_at) sliced to [offset, offset+limit). Empty messages and total_messages 0 when the run recorded no audit session (e.g. it failed before the agent started).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax message parts to return (default 100, max 200).
offsetNoNumber of parts to skip from the start of the run (default 0).
run_idYesAn agent-run id — the `id` of a `get_agent_details` `recent_runs` entry (also shown as `(run N)` in the agent's Recent Activity feed).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / run_id / description
      Previous value: -"An agent-run id — the `id` of a `get_agent_details` `recent_runs`\nentry (also shown as `(run N)` in the task's Recent Activity feed)."New value: +"An agent-run id — the `id` of a `get_agent_details` `recent_runs`\nentry (also shown as `(run N)` in the agent's Recent Activity feed)."
  2. Changed1 schema field changed
    • changedInput schema / properties / run_id / description
      Previous value: -"An agent-run id — the `id` of a `get_task_details` `recent_runs`\nentry (also shown as `(run N)` in the task's Recent Activity feed)."New value: +"An agent-run id — the `id` of a `get_agent_details` `recent_runs`\nentry (also shown as `(run N)` in the task's Recent Activity feed)."
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description goes well beyond the readOnlyHint annotation by disclosing pagination behavior, the meaning of has_more, and the edge case where a failed run records no audit session (empty messages, total_messages 0). This gives the agent realistic expectations about incomplete or empty results.

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 well structured with a summary paragraph, a usage paragraph, and a returns section. Every sentence earns its place, and the most important purpose is front-loaded before pagination details. No filler or 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?

Despite having no output schema, the description's returns block fully explains the response shape, including run_id, status, pagination fields, and the structure of the messages array. It also covers the empty-result edge case. An agent has everything needed to call and interpret this tool 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 input schema already documents all three parameters at 100% coverage with defaults and max values. The description adds useful complementary semantics by explaining the pagination loop ('Page with offset while has_more is true') and clarifying how offset slices the messages array, which is value beyond the raw schema.

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?

The description opens with a specific verb and resource: 'Read the transcript of one past background agent run — every tool call and reasoning step the agent recorded during that run.' This clearly identifies both the action and the scope, and distinguishes it from summary-level tools like get_agent_details.

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 explicitly says when to use it: 'Use this when a run's one-line summary isn't enough' with a concrete example. It also tells the agent where to get the required run_id (from get_agent_details recent_runs). It does not state explicit exclusions or compare against all alternatives, so it stops just short of a 5.

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

All Sliq 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