Skip to main content
Glama

goto_cue_tool

Jump to a specific cue number on a targeted executor or sequence. Specify cue ID and optionally executor or sequence to navigate directly.

Instructions

Jump to a specific cue.

Targets either an executor or a sequence. If neither is specified,
the command applies to the selected executor.

Args:
    cue_id: Target cue number
    executor: (Optional) Executor number
    sequence: (Optional) Sequence number

Returns:
    str: Operation result message

Examples:
    - Goto cue 5 on executor 4
    - Goto cue 3 in sequence 1

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cue_idYes
executorNo
sequenceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, and the description does not disclose side effects, prerequisites, or error conditions. It minimally states the operation but omits behavioral impact.

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?

The description is short, well-structured with header, args, returns, and examples. Every sentence adds value.

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?

Given the simple tool with an output schema, the description covers basics but misses error handling, constraints, and behavioral context. Adequate but not complete.

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?

Schema description coverage is 0%, and the description adds basic meaning for each parameter (e.g., 'Target cue number') but lacks details on ranges, formats, or constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it jumps to a specific cue, targeting an executor or sequence, which distinguishes it from sibling tools like store_cue or list_cues.

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

Usage Guidelines4/5

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

The description provides clear usage context and examples but lacks explicit exclusions or comparisons to alternatives like execute_sequence.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chienchuanw/gma2-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server