Skip to main content
Glama

renef_watch

Collects hook output for a bounded time window after hooks are installed, capturing prints from native or Java hooks. Use it to gather instrumentation results, with the duration capped at 60 seconds.

Instructions

Collect hook output for a time window (blocks, exclusive). Install hooks first (renef_hook_native / renef_hook_java), then call this to capture their prints. seconds capped at 60.

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_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
secondsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose key traits: the call blocks, it is exclusive, and the window is capped at 60 seconds. These are exactly the runtime characteristics an agent needs to avoid surprises. It does not explain what happens if no hooks are installed, which keeps it below a 5.

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 short sentences, zero filler, with the core action stated first and the prerequisite and cap following. Every sentence adds information an agent would otherwise have to guess.

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 single-parameter, blocking capture tool with an output schema already defining return values, the definition covers prerequisite, blocking/exclusive behavior, and the hard cap. Only edge-case behavior (empty results, concurrent sessions) is unstated.

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 0% and the single 'seconds' parameter has no description, so the description must compensate. It does, explaining that the parameter is a capture time window and is capped at 60. The default of 5 is conveyed only via the schema default, a minor residual gap.

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: 'collect hook output' within a 'time window', plus the qualifier 'blocks, exclusive'. That is far more informative than the bare name 'watch'. It does not explicitly contrast with siblings like renef_list_hooks or renef_server_logs, so a 4 rather than a 5.

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?

Gives explicit ordering guidance: install hooks first via renef_hook_native / renef_hook_java, then call this to capture their prints. That names the prerequisite tools and the sequencing condition. It stops short of stating when NOT to use it (e.g. after renef_disconnect), so 4.

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