Skip to main content
Glama

get_track_index

Retrieve the live overview and summary of a conductor track by reading its index.md file. Provide a track name to get the current track index.

Instructions

Read the index.md for a specific conductor track. Returns the live track overview and summary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
trackNameYes

Implementation Reference

  • MCP tool handler for 'get_track_index'. Calls manager.getTrackIndex(args.trackName) and returns the file content as text.
    server.tool(
      'get_track_index',
      'Read the index.md for a specific conductor track. Returns the live track overview and summary.',
      GetTrackIndexSchema.shape,
      async (args) => {
        const file = await manager.getTrackIndex(args.trackName);
        return {
          content: [{ type: 'text' as const, text: file.content }],
        };
      },
    );
  • Manager function getTrackIndex that validates the track slug and delegates to fs.readTrackFile to read 'index.md' from the track directory.
    async function getTrackIndex(trackName: string): Promise<TrackFile> {
      assertSafeSlug(trackName);
      return fs.readTrackFile(tracksDir, trackName, 'index.md');
    }
  • Low-level file system helper readTrackFile that reads a specific file (e.g., 'index.md') from a track directory and returns its content.
    async function readTrackFile(tracksDir: string, trackName: string, filename: string): Promise<TrackFile> {
      const filePath = join(tracksDir, trackName, filename);
      const content = await readFile(filePath, 'utf8');
      return { trackName, filename, content };
    }
  • Zod schema GetTrackIndexSchema defining the input: trackName (string, min 1).
    export const GetTrackIndexSchema = z.object({
      trackName: z.string().min(1),
    });
  • src/index.ts:52-52 (registration)
    Registration of conductor tools including 'get_track_index' via registerConductorTools.
    registerConductorTools(server, conductorManager);
Behavior3/5

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

No annotations are provided, so the description must carry full burden. It indicates a read operation (non-destructive) and mentions the return value, but does not disclose behavior like error handling or prerequisites (e.g., track must exist). Adequate but minimal.

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

Conciseness4/5

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

The description is very short (two sentences) with no unnecessary words. It front-loads the action and resource. Slight room for improvement in structure (e.g., listing return value first).

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?

For a simple tool with one parameter and no output schema, the description is mostly complete. It states what is read and what is returned. However, it lacks context about error conditions or the requirement for the track to exist.

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?

Schema description coverage is 0%, so the description should add meaning to the single parameter 'trackName'. It only mentions 'specific conductor track' but does not explain format, constraints, or examples. Insufficient compensation for lack of schema descriptions.

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 clearly states the action 'Read' and the resource 'index.md for a specific conductor track', with return value of 'live track overview and summary'. It is specific but does not explicitly differentiate from sibling tools like get_track_plan or get_track_spec.

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?

No guidance is provided on when to use this tool versus alternatives. The description simply states what it does without context for selection or exclusion.

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