Skip to main content
Glama

disconnect_app

Detach from the running app so tools revert to project-file operations, leaving the app open for continued editing.

Instructions

Stop driving the app; tools need a project file again. The app keeps running.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

The annotations only declare readOnlyHint=false and openWorldHint=false, so the description carries the burden of explaining behavior. It usefully discloses that 'the app keeps running' (no shutdown side effect) and that tool routing reverts to project files, but it omits error behavior and whether any unsaved app-side state is lost on disconnect.

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?

Two terse sentences with zero filler, and the state change is front-loaded ahead of the reassurance about the app staying alive. Every clause carries information.

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 no-parameter, no-output-schema toggle tool, the description covers the essential state transition and the key non-obvious fact that the app is not terminated. A note on the not-connected case or the connection state it clears would make it complete.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless schema applies. No misleading parameter language is present.

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 states a concrete action and its effect: it stops tools from driving the live app and returns them to project-file mode, which implicitly pairs with the sibling connect_app. The verb 'disconnect' is paraphrased rather than named, but the resource and state transition are unambiguous.

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 implied by the phrase 'tools need a project file again', which tells an agent this is the exit path from app-connected mode. However, it never states prerequisites (must currently be connected), what happens when not connected, or explicitly contrasts with connect_app/app_status.

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