Skip to main content
Glama

gc_dolphin_unfreeze

Resume a frozen Dolphin emulator process by sending SIGCONT to a specified instance, allowing execution to continue.

Instructions

Resume a frozen Dolphin process with SIGCONT.

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

Input Schema

NameRequiredDescriptionDefault
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 underlying mechanism (SIGCONT), which is genuinely useful behavioral context, but omits what happens on error (e.g. unknown or already-running instance) and any permission or state prerequisites.

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?

A single front-loaded sentence with zero filler; verb and resource come first and the mechanism follows. Nothing to trim.

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 one-parameter resume operation with no output schema, the description covers the core action adequately; only the instance_id semantics and non-frozen-instance behavior are missing, which are minor for a tool this simple.

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?

The single parameter is instance_id at 0% schema description coverage, and the description adds no meaning beyond the name — it doesn't say how to obtain an instance id or what identifies a valid one. With one self-describing param the baseline is roughly 3, and the description neither helps nor harms.

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?

States a specific verb ('Resume') and resource ('a frozen Dolphin process') plus the mechanism (SIGCONT), which makes the inverse relationship to gc_dolphin_freeze easy to infer. It doesn't explicitly name that sibling, but the purpose is 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?

'Resume a frozen process' implies when to use it (only against frozen instances), but there is no explicit when-not guidance, no mention of gc_dolphin_freeze as the counterpart, and no note about behavior on a non-frozen process.

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