Skip to main content
Glama

dev_stop

Stop a dev-loop session started by dev_start, optionally targeting a session ID or falling back to the active MCP or detached project session.

Instructions

Stop the dev-loop session started by dev_start.

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

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

A3.5/5.0
Behavior3/5

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

The annotations declare readOnlyHint=false, and "Stop" is consistent with a mutating operation, so there is no contradiction. Beyond that, the description adds nothing about what is terminated, whether the call is idempotent, or what happens when no session exists; the fallback chain is only visible in the schema.

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?

One sentence, front-loaded with the verb, and it identifies the session lineage immediately. There is no filler or redundancy.

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

Completeness3/5

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

For a simple one-optional-param mutation with no output schema, the definition is minimally adequate, but it omits error behavior when no session is found and gives no indication of what a successful stop returns or whether the operation is repeatable.

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?

There is a single optional parameter with 100% schema description coverage, so the schema already explains that session_id falls back to the server-held dev_start session and then to project detach state. The description adds no meaning beyond that and simply assumes the implicit target.

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?

The description gives a specific verb ("Stop") and a specific resource ("the dev-loop session started by dev_start"), and it anchors the target to the sibling that creates it. It does not, however, distinguish itself from the sibling named stop_session, which an agent could reasonably confuse with this tool.

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

Usage Guidelines3/5

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

Usage is only implied through the reference to dev_start: use this to tear down what dev_start created. There is no explicit statement of when not to use it, no mention of stop_session as an alternative for non-dev sessions, and no prerequisites such as requiring an active session.

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