Skip to main content
Glama

list_tracks

List all active conductor tracks with a plan.md to understand current work in progress.

Instructions

List all live conductor tracks (only tracks with a plan.md are returned). Use to understand current work in progress.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'list_tracks': registers the tool on the server, calls manager.listTracks() and returns JSON-stringified track summaries.
    export function registerConductorTools(server: McpServer, manager: ConductorManager): void {
      server.tool('list_tracks', 'List all live conductor tracks (only tracks with a plan.md are returned). Use to understand current work in progress.', ListTracksSchema.shape, async () => {
        const tracks = await manager.listTracks();
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(tracks, null, 2) }],
        };
      });
  • Schema for list_tracks: empty object (no input parameters).
    export const ListTracksSchema = z.object({});
  • Registration of the 'list_tracks' MCP tool via server.tool() with name 'list_tracks'.
    export function registerConductorTools(server: McpServer, manager: ConductorManager): void {
      server.tool('list_tracks', 'List all live conductor tracks (only tracks with a plan.md are returned). Use to understand current work in progress.', ListTracksSchema.shape, async () => {
        const tracks = await manager.listTracks();
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(tracks, null, 2) }],
        };
      });
  • Manager-level listTracks: delegates to FileSystemAccess.listTracks() and wraps results in TrackSummary objects.
    async function listTracks(): Promise<TrackSummary[]> {
      const names = await fs.listTracks(tracksDir);
      return names.map((name) => ({ name, hasPlan: true }));
    }
  • Low-level filesystem implementation: reads tracks directory, filters to subdirectories containing plan.md.
    async function listTracks(tracksDir: string): Promise<string[]> {
      const entries = await readdir(tracksDir, { withFileTypes: true });
      const tracks: string[] = [];
      for (const entry of entries) {
        if (entry.isDirectory()) {
          const planPath = join(tracksDir, entry.name, 'plan.md');
          if (existsSync(planPath)) {
            tracks.push(entry.name);
          }
        }
      }
      return tracks;
    }
Behavior3/5

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

No annotations provided, so description must disclose behaviors. It reveals the filtering condition (only tracks with plan.md) but does not mention read-only nature, performance, or auth needs.

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?

Two sentences, no extraneous words. Front-loaded with action and filter. Efficient for its purpose.

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 tool simplicity (no params, no output schema), description covers purpose and filter adequately. Could briefly differentiate from 'get_track_index' for completeness, but not necessary.

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?

Input schema is empty with 100% coverage, so no parameters to describe. Baseline for 0 params is 4; description adds no additional parameter info but none is needed.

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?

Describes specific verb 'list' and resource 'live conductor tracks', with clear filter 'only tracks with a plan.md'. Distinguishes from siblings like 'get_track_index' or 'create_track' by specifying the scope.

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?

States use case 'to understand current work in progress' but does not mention when not to use or provide alternatives. Lacks explicit differentiation from other list-like tools.

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/2loch-ness6/mempalace-mcp-dev'

If you have feedback or need assistance with the MCP directory API, please join our Discord server