Skip to main content
Glama
Sign In

Traceo

by io.github.muhamad-0
OverviewDiscussionsAdmin

Get recording timeline

get_timeline
Read-onlyIdempotent

Console logs, network requests and user actions merged in time order, with times relative to recording start (+12.4s). Best view for reproducing a bug. Narrow with from_s/to_s around an error.

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": {
      "recording": "<recording>"
    },
    "name": "get_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_sNoEnd, in seconds from recording start.
limitNoMax lines to return.
typesNoEvent kinds to include (default all).
cursorNoPagination cursor from a previous call.
from_sNoStart, in seconds from recording start.
recordingYesTraceo share link (e.g. https://www.traceo.dev/abc123...) or recording id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: merged time-ordered output and timestamps relative to recording start (+12.4s). It does not cover result volume or pagination behavior (limit max 200, cursor), leaving that to the schema.

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?

Two tight sentences, front-loaded with what the tool returns and followed by the practical narrowing tip. No redundant or filler wording.

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

Completeness4/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 usefully explains the shape of the result (merged, time-ordered, relative timestamps), which is exactly the missing piece. The remaining gap is pagination/limit behavior, which the schema covers but the description does not surface.

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 coverage is 100%, so every parameter is already documented, including the relative-seconds semantics of from_s/to_s. The description reinforces the intended use of the range parameters (narrowing around an error) but adds no syntax or format detail beyond the schema — baseline 3 applies.

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 names the three data streams (console logs, network requests, user actions) and states they are merged in time order, which is a precise characterization of the resource. Implicitly distinguishes itself from the get_console_logs / get_network_requests / get_user_actions siblings by being the merged view, though it never names them.

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?

"Best view for reproducing a bug" gives clear situational context, and "Narrow with from_s/to_s around an error" gives a concrete tactic. No explicit when-not guidance or named alternatives, so not a 5.

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

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