Skip to main content
Glama

gc_instance_remove

Stops a Dolphin emulator instance and deletes its data directory, cleaning up resources when an emulated or registered hardware session is no longer needed.

Instructions

Stop and delete an instance and its data directory.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "instance_id": "<instance_id>"
    },
    "name": "gc_instance_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the critical behavior — the instance's data directory is deleted, so state is destroyed, not just stopped — but says nothing about permissions, irreversibility guarantees, or what happens if the instance does not exist.

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?

A single short sentence with the destructive outcome front-loaded alongside the verb; nothing is wasted. It is terse to the point of under-specification, but structurally sound.

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 one-parameter, no-output-schema teardown tool, the minimum useful information (that data is deleted) is present. Missing are the preconditions for calling it and any hint about the identifier argument, which the surrounding structured data does not supply.

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

Parameters2/5

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

Schema description coverage is 0%, so the single required parameter instance_id is documented nowhere. The description never mentions the identifier, its expected format, or where to obtain it (e.g., from gc_instance_list), so the description does not compensate for the schema gap.

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 uses a specific verb pair ("Stop and delete") on a specific resource ("an instance and its data directory"), which is more informative than the name alone. It does not explicitly distinguish itself from the close sibling gc_instance_stop, leaving the agent to infer that this one is destructive while that one is not.

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: the tool is for tearing down an instance entirely. There is no explicit statement of when to prefer it over gc_instance_stop, no preconditions (must the instance be running?), and no guidance on confirming the destruction beforehand.

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