Skip to main content
Glama

gc_controller_sequence_cancel

Cancels a running input sequence on a specified emulator instance, stopping further queued controller actions when that sequence is no longer needed.

Instructions

Cancel a running input sequence.

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>",
      "sequence_id": "<sequence_id>"
    },
    "name": "gc_controller_sequence_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
instance_idYes
sequence_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does not state whether cancellation is immediate or deferred, whether already-emitted inputs are released, what happens if sequence_id is not running, whether it requires the sequence to have been started on the same instance_id, or what the response contains. For a state-changing control tool that is a substantial gap.

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?

One short, front-loaded sentence with zero filler and the verb leading. The brevity is structurally clean, though it borders on under-specification rather than true conciseness.

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

Completeness2/5

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

With two required undocumented parameters, no annotations, and no output schema, the description is too thin for the tool's complexity. It omits error conditions, post-cancellation state, and how the sequence_id is obtained.

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%, and both parameters are required. The description adds nothing about instance_id (which controller instance?) or sequence_id (where the id comes from, its format, or whether it identifies a previously started sequence), leaving both identifiers defined only by their titles.

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?

"Cancel a running input sequence" gives a specific verb (cancel) and resource (input sequence), so the agent knows exactly what operation is performed. It does not, however, distinguish this from the likely counterpart gc_controller_sequence that starts a sequence, leaving the start/stop pairing to inference.

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

Usage Guidelines2/5

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

The word "running" hints that the sequence must be active, but there is no explicit when-to-use, no when-not-to-use, and no naming of alternatives such as gc_controller_sequence. An agent must guess that this is the teardown counterpart to sequence start.

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