Skip to main content
Glama

trace_correlate

Correlate traceIds across frontend evidence and backend logs, validate trace coverage, and trace full request chains from browser to backend.

Instructions

traceId 深度关联工具(v1.9.5 起合并 browser_trace_chain 和 trace_correlation_check)。通过 mode 参数区分子模式:view(默认,根据 traceIds 反查前端证据包和后端日志,实现前后端联调闭环)/ check(校验浏览器请求和后端日志是否共享同一 traceId/runId,输出 trace 覆盖率和关联性评分,等价于已废弃的 trace_correlation_check)/ chain(全链路调用链追溯,从 traceId 或时间点追溯前端→API→后端的完整请求链路,等价于已废弃的 browser_trace_chain)。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL 包含过滤(mode=chain 时使用)
modeNo关联模式:view(默认,traceId 深度关联)/ check(trace 覆盖率校验,等价于 trace_correlation_check)/ chain(全链路调用链追溯,等价于 browser_trace_chain)view
sinceNo只检查此 ISO 时间点之后的请求(mode=check 时使用),默认使用当前 checkpoint
traceIdNo单个 traceId(与 traceIds 二选一,mode=view/chain 时使用)
traceIdsNo要关联的 traceId 列表(mode=view 时使用)
statusMinNo最小 HTTP 状态码过滤(mode=chain 时使用,如 400 只显示错误请求)
urlContainsNo只检查 URL 包含此字符串的请求(mode=check 时使用)
useSshBackendNo是否通过 SSH 远程查询后端日志(需配置 backend_logs 工具)
backendLogPathNo后端日志文件本地路径,将在文件中搜索 traceId
backendLogLinesNo每个 traceId 返回的后端日志行数上限,默认 10
includeBackendLogsNo是否同时从后端服务器 grep 日志(mode=chain 时使用,需要 SSH 免密)
Behavior3/5

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

No annotations are provided, so the description bears full responsibility. It discloses the tool's modes and their effects but does not mention idempotency, authorization requirements, rate limits, or side effects. The description implies read-like operations but lacks explicit behavioral traits.

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?

Description is a single paragraph of moderate length. It front-loads the key fact (merged tool) and then systematically explains modes. It is efficient with no filler, though could be slightly more structured (e.g., bullet points for modes).

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description should explain return values, but it does not. Given the tool's complexity (11 parameters, 3 modes), the description covers usage context well but omits output format and behavior. The relationship with deprecated siblings is clarified, but completeness is partially lacking.

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?

Schema coverage is 100%, so baseline is 3. The tool description adds value by explaining the meaning of the 'mode' parameter values and their equivalence to deprecated tools, and provides overall context for parameter usage (e.g., 'since' used in check mode). This enhances understanding beyond the schema descriptions.

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?

Description clearly states 'traceId 深度关联工具' and explicitly mentions it merges two previous tools (browser_trace_chain and trace_correlation_check), providing a distinct identity. It explains three sub-modes (view/check/chain) with specific use cases, effectively distinguishing itself from siblings like browser_trace_chain and trace_correlation_check.

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?

Description explicitly defines when to use each mode (e.g., 'view' for front-end/back-end debugging, 'check' for trace coverage verification, 'chain' for full link tracing). It implies this tool replaces the deprecated browser_trace_chain and trace_correlation_check, providing clear context. However, it does not explicitly state scenarios where the tool should not be used.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/validpilot/ai-verify-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server