Skip to main content
Glama
Podcast MCP
by calebn

record_tracks_tool

Shows which track each recorded person lands on, matching names to existing, new, or ambiguous tracks and explaining the reason in plain words. Host only.

Instructions

Show which track each recorded person lands on (matched by name to an existing track, new, or ambiguous, which also covers a track already used by someone else: reason track_in_use), with a plain-words reason. Host only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "record_tracks_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it implies a read-only 'show' operation and discloses the reason taxonomy, including that 'ambiguous' folds in a track already used by someone else. What it does not clarify is whether this only inspects/derives the mapping or actually performs the assignment, which is the single most important behavioral question for an agent choosing between this and record_assign_track_tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence with no padding, but heavy parenthetical nesting makes the outcome categories hard to parse on first read. The core purpose is front-loaded, so the density is a style cost rather than a correctness problem.

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?

An output schema exists, so the return shape need not be explained, and the description does cover the classification semantics and the host-only restriction. However, for a tool that could be confused with the adjacent assign/land tools, the missing distinction between previewing and committing a mapping is a real completeness gap.

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

Parameters2/5

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

The schema has one parameter, project_path, with 0% description coverage and no enum or constraint, and the description never mentions it. With zero schema documentation, the description should explain what project_path means and whether null selects a default project, which it entirely omits.

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 states a specific verb and resource ('Show which track each recorded person lands on') and enumerates the three outcome categories it reports: matched, new, and ambiguous. The naming of the 'track_in_use' reason makes the scope concrete, though the tool name itself reads like it records audio tracks, so the description is doing necessary disambiguation work.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no routing to alternatives, even though sibling tools such as record_assign_track_tool and record_land_tool plausibly overlap. 'Host only' is a useful access constraint but is stated without explaining what a non-host caller should do instead.

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