Skip to main content
Glama
Podcast MCP
by calebn

record_assign_track_tool

Assign a participant's recordings to an existing track or a new one, with staging and replace rules.

Instructions

Correct a person's track: put their recordings on an existing track id, or pass track="new" for a new one. Allowed until the session is accepted; one undo step when takes are already staged; a replace follows the person and returns to their old track once no staged take or bed of theirs is left, unless a staged take or bed sits on either track or another person holds it by choice or by an acknowledged, non-tombstoned take (the moved person's own pin or take does not block). Refusal codes: unknown_participant, unknown_track, track_taken, replace_target_track, person_removed, session_already_accepted, session_skipped.

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": {
      "participant_id": "<participant_id>",
      "track": "<track>"
    },
    "name": "record_assign_track_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackYes
project_pathNo
participant_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the undo behavior ('one undo step when takes are already staged'), the semantics of replacement, the blocking ownership rules, and a full list of refusal codes. The middle sentence describing replace/blocking logic is extremely dense and hard to parse, and no permission or auth requirements are stated, so it falls short of a 5.

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 definition is well-sized and front-loaded: the correction action and the two track modes come first, the eligibility constraint next, the blocking logic after, and the refusal codes last. There is no filler — every clause carries operational meaning, even if the replace sentence requires careful reading.

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?

This is a mutation tool with no annotations and zero schema descriptions, so the description must supply safety and behavioral context — and it largely does, covering eligibility, undo, replacement side effects, blocking rules, and the complete failure taxonomy. The output schema handles return values, but `participant_id` and `project_path` remain unresolved and no permission model is given, leaving a modest gap.

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% across three parameters, so the description must compensate. It does explain the semantics of `track` well (existing id vs. the literal "new"), but `participant_id` and `project_path` are never explained — not even whether project_path is required for disambiguation across projects. Partial compensation only.

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?

The description opens with a specific verb and resource — 'Correct a person's track' — and immediately clarifies the two modes (existing track id vs. track="new"). This clearly separates it from siblings like track_set_media_tool or speaker_gate_track_tool, though no sibling is named explicitly, which is the only thing keeping it from a 5.

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?

It states a concrete applicability window ('Allowed until the session is accepted') and enumerates the conditions under which a reassign is blocked, which effectively defines when the tool will fail versus succeed. It does not route the agent to any alternative tool for the blocked cases, so the when-to-use guidance is strong but not complete.

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

Deploy Server

Other Tools