Skip to main content
Glama
paramount-engineering

Roku Dev Studio MCP Server

by paramount-engineering
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Debugger: Wait for Stop

debugger_wait_for_stop
Read-onlyIdempotent

Block until a Roku debug session halts at a breakpoint, step, or error, then retrieve top-frame stack and variables. Returns a timeout if still running.

Instructions

Block (server-side poll) until the target HALTS at a breakpoint / STOP / step-completion / runtime error, then return { stopped: true, stop: { reason, detail, threads, stackFrames, variables } } — the top-frame snapshot. Returns { stopped: false, timedOut: true } if it is still running at the deadline, or { stopped:false, state } if the session ended. Call this right after debugger_continue / debugger_step, or after triggering the app, to know when you can inspect. Optional timeoutMs (default 15000, max 30000).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceNoOptional. Roku IP or serial; must match a connected Dev Studio tab. Omit to use the focused tab.
timeoutMsNoMax ms to wait (default 15000, capped at 30000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.2

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses blocking server-side polling, timeout behavior, successful halt results, timed-out results, and session-ended results.

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?

The description is dense and well structured, with the primary blocking behavior front-loaded and return conditions plus usage guidance in compact sentences. The only minor repetition is the timeout default, but it does not hurt clarity.

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

Completeness5/5

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

Given there is no output schema and only two optional parameters, the description fully covers all return scenarios and specific usage context, leaving no important gap for an agent.

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% with both parameters already described in the input schema. The description only repeats the timeoutMs default/max and adds no new semantic detail beyond the schema.

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?

The description clearly states the tool blocks until the target halts and returns a snapshot, using a specific verb and resource. It distinguishes itself from sibling debugger actions by focusing on waiting for a halt rather than initiating continue/step/pause.

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

Usage Guidelines5/5

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

It explicitly says to call it right after debugger_continue/debugger_step or after triggering the app, which tells the agent exactly when to use it to know when inspection is possible.

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