Skip to main content
Glama

create_timecode_pool

Creates a timecode pool object, labels it, and binds it to a timecode slot for cue triggering.

Instructions

Create a timecode show, optionally naming it and assigning a slot.

Standard SMPTE setup: store the timecode pool object, label it, and bind it
to a timecode slot for cue triggering. Timecode events themselves are
recorded in real time via control_timecode(action="record").

Args:
    tc_id: Timecode show ID
    name: Optional display name
    slot: Optional timecode slot to assign

Returns:
    str: Operation result message

Examples:
    - Create timecode 1 named "Act 1" on slot 1

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tc_idYes
nameNo
slotNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description explains the creation process and return value. Without annotations, it carries the full burden and covers basic behavior. However, it lacks disclosure about idempotency or handling of duplicate tc_ids.

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 efficiently structured with a purpose statement, context, parameter list, return type, and example. Every sentence is necessary and adds value.

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?

The description is fairly complete for a creation tool, covering purpose, parameters, and return. Minor omission: not addressing conflict when tc_id already exists. Still, adequate given simplicity.

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?

Schema description coverage is 0%, so the description fully compensates by explaining all three parameters (tc_id, name, slot) and providing an example. 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 'Create a timecode show' with optional naming and slot assignment. It distinguishes from sibling tools like control_timecode and assign_timecode_slot by focusing on creation, and provides additional context about SMPTE setup.

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?

The description mentions that timecode events are recorded via control_timecode, implying when to use this tool vs that one. However, it does not explicitly state when not to use this tool or provide alternatives for specific scenarios like reassigning slots.

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