Skip to main content
Glama
Sign In
Cloady

Cloady

Official
by Cloady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Read Trace

readTrace
Read-only

Retrieve a trace's spans in tree order with service, timing, status, first exception and attributes, limited to the workspace's apps. Use it to debug distributed requests.

Instructions

Returns the spans the workspace's apps sent in a trace, in tree order, with each span's service, timing, status, first exception and attributes. Spans from outside the workspace are left out. Answers 404 when no span of the trace belongs to the workspace, it was sampled out, or it is older than 7 days.

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": {
      "workspaceSlug": "<workspaceSlug>",
      "traceId": "<traceId>"
    },
    "name": "readTrace"
  }
}

Input Schema

NameRequiredDescriptionDefault
aroundNoUnix milliseconds near the trace, such as a log line's time, which narrows the lookup
traceIdYesTrace id, up to 32 hex characters
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the read-only, non-destructive, open-world safety profile, and the description adds real context on top: tree ordering, cross-workspace span filtering, sampling behavior, and the 7-day retention window behind 404s. It stops short of describing result size limits or pagination, which matters for large traces.

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?

Three tight sentences: what is returned and in what shape, the scoping rule, then the failure conditions. Every sentence carries distinct information and the returned-data description is front-loaded.

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 takes on the burden of describing returns and does so at field level (service, timing, status, first exception, attributes). Combined with the explicit 404 conditions, an agent has enough to call correctly; only limits and pagination behavior are missing.

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?

At 67% schema coverage, traceId and around are already documented in the schema, and the description adds nothing about their format or interaction. workspaceSlug has no schema description and is likewise unexplained in the description, so the coverage gap is not compensated.

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 a specific verb and resource ('Returns the spans ... in a trace') and even specifies ordering and the per-span fields returned, so an agent knows exactly what this yields. It does not, however, contrast itself with nearby siblings such as searchServiceTraces or getAppTracing, leaving the agent to infer the single-trace vs. search distinction.

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?

Usage is implied by the requirement of a traceId plus workspace scope, and the 404 clause tells the agent when the call will fail. There is no explicit guidance on when to prefer this over searchServiceTraces, nor any statement of prerequisites (e.g. token scopes).

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

Deploy Server

Other Tools