Skip to main content
Glama

label_sequence_cue

Assign a label to a cue or range of cues within a named sequence, using sequence ID or name to identify the context.

Instructions

Label a cue within a specific sequence.

This tool addresses cues through the sequence context, which is required
for labeling cues inside named sequences.

Args:
    sequence: Sequence ID or name (e.g., "100" or "Set List")
    cue_id: Cue number within the sequence
    name: Label to assign
    end_cue: (Optional) End cue for range labeling

Returns:
    str: Operation result message

Examples:
    - Label cue 1 in "Set List" as "Opening+Childhood"
    - Label cue 1 in sequence 100 as "Opening+Childhood"
    - Label cues 1 thru 5 in "Set List" as "Act 1"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sequenceYes
cue_idYes
nameYes
end_cueNo

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, so the description carries full burden. It states that it labels a cue and can label a range with an optional end_cue, but does not disclose whether it overwrites existing labels, requires permissions, or other side effects. The behavioral impact is inadequately covered.

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 concise and well-structured with an intro, Args, Returns, and Examples. Every sentence is informative, and examples are provided without unnecessary verbosity.

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?

Given the tool has 4 parameters, no annotations, and an output schema, the description covers the main functionality and parameter details well. However, it lacks information about error cases, prerequisites (e.g., sequence existence), and result message specifics, leaving minor gaps.

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

Parameters5/5

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

The schema has 0% description coverage, so the description must compensate. It provides clear parameter descriptions in the Args section with examples, including the optional end_cue and acceptable formats for sequence. This adds significant meaning beyond the bare schema.

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 the tool labels a cue within a specific sequence, using a specific verb and resource. It distinguishes from sibling tools like 'label_cue_across_sequences' by emphasizing sequence context.

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 explains that the tool is for labeling cues inside named sequences via sequence context, but does not explicitly mention when not to use it or provide alternatives. It implies the correct use case but lacks exclusions.

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