Skip to main content
Glama
Sign In
Delve MCP

Delve MCP

by dwisiswant0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

replay

Replay an rr trace to debug Go programs, specifying the trace path and optional process ID.

Instructions

Replay an rr trace

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": {
      "tracePath": "<tracePath>"
    },
    "name": "replay"
  }
}

Input Schema

NameRequiredDescriptionDefault
tracePathYesPath to the rr trace directory
onProcessNoOptional PID to pass to rr

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, and the description does not disclose behavioral traits such as side effects, permissions, or whether the replay is destructive. The description carries full burden but fails to provide meaningful transparency.

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?

The description is a single clear sentence with no waste. It is appropriately short for a two-parameter tool, though it could optionally be a bit more informative.

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?

Given no output schema and full schema coverage, the description provides minimal but sufficient context. However, it lacks detail on expected behavior or output, which would be helpful for an action like replaying a trace.

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 description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the schema's parameter descriptions.

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 'Replay an rr trace' clearly states a specific verb and resource, distinguishing it from sibling debugging commands like 'continue' or 'step'. However, it does not explicitly differentiate itself or add context beyond the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives or any prerequisites. The description is purely definitional.

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