Skip to main content
Glama

Trace status

trace_status
Read-only

View recent traced tool calls and buffer status without opening log files. Use it to check what ran recently and verify trace output availability.

Instructions

Show recent traced tool calls (tracing is always on). Use when: you want to see what ran recently without opening the log file. Avoid when: tracing is off (the buffer is empty). Output: enabled, file, buffered, recent[] (newest first, timestamp_ms is epoch milliseconds).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "trace_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many recent traces to return (default 20, max 100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavior: tracing is always on, results come from a buffer, and they are ordered newest-first. It stops short of stating buffer size, retention, or what happens on overflow, which is the main behavioral unknown for a buffered reader.

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?

Four short labeled lines with the purpose front-loaded and no filler — well suited for scanning. The only blemish is the redundancy between '(tracing is always on)' and the 'Avoid when tracing is off' line, which spends a sentence on a condition that cannot occur.

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 correctly compensates by enumerating the return shape (enabled, file, buffered, recent[]) and the epoch-millisecond timestamp convention. Combined with annotations and full schema coverage, that is nearly complete; only buffer size or retention limits are unstated.

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% and the single 'limit' parameter is fully documented in the schema (default 20, max 100). The description adds no parameter meaning beyond that, so the baseline 3 applies; the 'recent[]' and 'timestamp_ms' notes describe output, not input semantics.

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?

States a specific verb and resource: 'Show recent traced tool calls', with a scoping note that tracing is always on. It does not name a sibling such as read_audit or recent_files to differentiate itself, so an agent must infer the distinction from names alone.

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?

Provides explicit 'Use when' and 'Avoid when' framing, which is more than most definitions offer. However, the 'Avoid when: tracing is off' clause is undercut by the earlier parenthetical '(tracing is always on)', making the exclusion effectively vacuous and slightly self-inconsistent.

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