Skip to main content
Glama

renef_backtrace

Prints the current thread call stack in the target process, helping you inspect execution flow during hook debugging.

Instructions

Print the current thread call stack in the target process (useful inside hook debugging).

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": "renef_backtrace"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. "Print" implies a non-destructive read and "target process" hints that an attachment context is required, but the description never states the prerequisite (attach state), whether the stack is captured live or snapshotted, or that the call fails without a target.

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?

One short sentence with the action front-loaded and the only qualifier (hook debugging) placed in a tight parenthetical. Nothing is repeated or wasted.

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?

For a zero-parameter diagnostic with an output schema describing the returned stack, the definition covers what the tool does and where it helps. The remaining gap is the operational precondition — that a target process must be attached — which an agent only learns by inference from "target process".

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?

The tool takes zero parameters, so the baseline is 4; there is no parameter semantics to add and the description correctly does not invent any. No schema burden is left unmet.

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?

"Print the current thread call stack in the target process" gives a specific verb (print) plus resource (call stack) plus scope (current thread, target process). It is concretely understandable on its own, though it does not contrast itself with any sibling such as renef_list_hooks or renef_exec, so disambiguation relies on the reader's familiarity with the domain.

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?

The parenthetical "useful inside hook debugging" implies the intended situation, which is more than nothing. But there is no explicit statement of when to reach for this versus hook listing or script inspection, and no stated preconditions or exclusions.

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