Skip to main content
Glama

set_cue_cmd

Set a command to execute automatically when a cue fires. Commonly used to trigger macros or sequence operations.

Instructions

Assign a command to a cue's CMD field.

When the cue fires, the assigned command will execute automatically.
Common use: trigger a macro when a cue runs.

Args:
    cue_id: Cue number
    sequence_id: Sequence number
    command: Command to execute when cue fires (e.g., "Macro 101")

Returns:
    str: Operation result message

Examples:
    - Set cue 1 in sequence 100 to trigger "Macro 101"
    - Set cue 5 in sequence 200 to run "Go Sequence 10"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cue_idYes
sequence_idYes
commandYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Explains that command executes automatically when cue fires, which is key behavioral info. No annotations provided, so description carries burden; could mention side effects or error handling, but adequate.

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?

Front-loaded with summary, then structured Args, Returns, Examples. No redundant information, every sentence earns its place.

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

Completeness5/5

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

For a tool with 3 simple parameters and clear behavior, description is complete. Includes return type and examples. Output schema exists but is not needed.

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?

Schema coverage is 0%, but description adds meaning with 'Args' section explaining each parameter (cue number, sequence number, command example). Covers all 3 parameters clearly.

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?

Description clearly states verb ('assign'), resource ('cue's CMD field'), and purpose ('execute command on cue fire'). Distinguishes from siblings like run_macro.

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?

States common use case and provides examples, but lacks explicit when-not-to-use or comparison to alternative tools like set_macro_line.

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