Skip to main content
Glama

relaunch_app

Restart the app under test with a cold start while preserving its data, so you can verify that state persists across restarts. Log streaming continues through the restart.

Instructions

Close the app under test and start it again: a cold start that keeps the app's data, e.g. to check that something persists. Its log keeps streaming across the restart. Not available on embed sessions.

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

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.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, so the description carries most of the weight, and it delivers: state is preserved across the restart, logs continue streaming, and the tool is unavailable on embed sessions. It does not say whether in-flight sessions or unsaved UI state are lost beyond the data caveat, but the key mutation semantics are disclosed.

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-loads the core action in the first clause, then adds two short qualifying facts with no filler. Every clause carries information, though the sentence is dense in a way that slightly blurs the availability caveat into the behavioral note.

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-optional-parameter, no-output-schema tool, the description covers action, data-persistence semantics, log continuity, and availability limits. The only remaining ambiguity is what the call returns, which is mitigated by the simplicity of the operation.

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%, and the schema itself documents the session_id fallback chain in detail. The description adds nothing about session_id, 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 a specific verb pair (close and start again) plus the resource (the app under test), and qualifies the restart as a cold start that preserves app data. The 'cold start that keeps the app's data' detail distinguishes it from a hot-reload sibling without needing to name one.

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?

Provides a concrete motivating scenario ('e.g. to check that something persists') and an explicit exclusion ('Not available on embed sessions'), which tells an agent when it cannot be called. It stops short of naming a sibling such as dev_reload as the alternative, so routing between restart and reload is left implicit.

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