Skip to main content
Glama

dev_reload

Rebuilds, uploads and reloads a Roku channel into an active vibeview dev session after code changes, then waits for the device restart so you can verify the UI.

Instructions

Roku only: re-package the channel with the build command from vibeview.json (platforms.roku.build), upload it, and reload it into the session dev_start is holding (or, with no held session, this project's vibeview dev --detach session) — the MCP equivalent of pressing r in vibeview dev. Returns once the device restarts the channel (a few seconds); call ui_tree afterwards. Other platforms hot-reload through Metro and need no call.

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

Input Schema

NameRequiredDescriptionDefault
session_idNoSession ID to target. Optional: falls back to the MCP-server-held dev_start session, then this project's `vibeview dev --detach` state, if either is available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only supply readOnlyHint=false, so the description carries most of the burden and does well: it discloses that the tool performs a build, upload, and device-side reload, that it blocks until the device restarts the channel (a few seconds), and that it is the programmatic equivalent of a dev-keypress. It stops short of naming failure modes (build errors, no attached device) or what happens to a held session on failure.

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?

Front-loaded with the platform restriction, which is the most decision-relevant fact. The middle is a dense em-dash-chained sentence with three parenthetical qualifications, but each clause carries real information rather than filler.

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 mutation tool with no output schema, the definition covers everything an agent needs: platform gating, the source of the build command, session resolution, blocking duration, and the recommended next call. Nothing material about correct invocation is missing.

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% and the single session_id parameter already documents the fallback chain to the MCP-held dev_start session and the detached session. The description restates that same chain, adding little meaning beyond the schema, so the baseline of 3 applies.

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?

States specific verbs and resources: re-package the channel using platforms.roku.build, upload it, and reload it into a dev session. It immediately scopes itself ('Roku only') and anchors to a concrete analogy ('the MCP equivalent of pressing `r` in `vibeview dev`'), so an agent can distinguish it from dev_start, dev_stop, or relaunch_app without opening any schema.

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?

Explicitly names the when-not condition ('Other platforms hot-reload through Metro and need no call') and the follow-up step ('call ui_tree afterwards'). It also explains the session resolution order, so an agent knows the call works even without an explicit session target.

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