Skip to main content
Glama
paramount-engineering

Roku Dev Studio MCP Server

by paramount-engineering
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Network Inspector: List Events

network_inspector_list_events
Read-onlyIdempotent

List captured network events as concise summaries, with optional filters by device, host, method, status, or error class to pinpoint issues without exposing full headers.

Instructions

List captured network events as lightweight summaries (no full headers/body — drill down with network_inspector_get_event_detail using an event id). Summary-first by design to protect context. All filters optional and AND-combined across fields; give a field an array to OR within it (e.g. status: [404, 500]): device (IP or serial; omit for all Rokus on the hotspot), host (case-insensitive substring of hostname/SNI/URL), method (GET/POST/…), type (one of the network event types), status (exact HTTP response status code(s)), statusClass ('2xx'|'3xx'|'4xx'|'5xx'), contentType (case-insensitive substring against the response Content-Type, e.g. "json"), errorsOnly (HTTP status >= 400 — a shortcut for statusClass 4xx+5xx), mitmOnly (decrypted-HTTPS transactions only), limit (default 200, max 2000). Returns most-recent events. Requires Network Inspector enabled (see network_inspector_status).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoOptional case-insensitive substring matched against hostname, TLS SNI, or request URL.
typeNoOptional event type filter.
limitNoMax events to return (default 200, max 2000).
deviceNoOptional Roku IP or serial. Omit to include every Roku on the hotspot.
methodNoOptional HTTP method filter (e.g. "GET", "POST").
statusNoOne or more values to match (OR).
mitmOnlyNoOnly decrypted-HTTPS transactions captured via the MITM proxy.
errorsOnlyNoOnly HTTP transactions with a response status >= 400.
contentTypeNoOne or more values to match (OR).
statusClassNoOne or more values to match (OR).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.2

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, and the description adds substantial behavior beyond those: summary-first design to protect context, AND-OR filter composition, most-recent ordering, errorsOnly as a shortcut, and the requirement on Network Inspector being enabled. No contradictions with annotations.

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 but efficiently organized: core action and summary-vs-detail distinction first, then filter semantics, then ordering and prerequisites. Every clause earns its place, and the use of parentheticals keeps the long filter list compact without losing precision.

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?

For a tool with 10 optional filters and no output schema, the description covers all filter behaviors, result shape (lightweight summaries with event IDs), ordering (most-recent), prerequisite status, and the path to more detail. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though schema coverage is 100%, the description adds critical semantic value: filters are AND-combined, arrays OR within a field, with a concrete example (status: [404, 500]). It also clarifies defaults, case-insensitive substring matching, the meaning of errorsOnly, and the omit-device shortcut — all beyond the parameter descriptions in 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 states a specific verb and resource ('List captured network events') and immediately differentiates itself from the detail-retrieval sibling by noting it returns 'lightweight summaries (no full headers/body — drill down with network_inspector_get_event_detail)'. This makes its role in the Network Inspector family unmistakable.

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 provides the when-to-use alternative: use this for summaries, drill down with network_inspector_get_event_detail for full details. It also states the prerequisite ('Requires Network Inspector enabled (see network_inspector_status)') and clarifies the default scope (all Rokus when device is omitted).

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