Skip to main content
Glama

get_track_plan

Reads the plan.md file for a given conductor track and returns its live content, enabling access to current file data instead of outdated docs or memory.

Instructions

Read the plan.md for a specific conductor track. Returns live file content — not docs, not memory.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
trackNameYes

Implementation Reference

  • Registration of the 'get_track_plan' MCP tool via server.tool(), with the schema and handler.
    server.tool('get_track_plan', 'Read the plan.md for a specific conductor track. Returns live file content — not docs, not memory.', GetTrackPlanSchema.shape, async (args) => {
      const plan = await manager.getTrackPlan(args.trackName);
      return {
        content: [{ type: 'text' as const, text: plan.content }],
      };
    });
  • Zod schema for get_track_plan: requires a 'trackName' string parameter.
    export const GetTrackPlanSchema = z.object({
      trackName: z.string().min(1),
    });
  • Handler/implementation: getTrackPlan() validates the slug via assertSafeSlug() and delegates to fs.readTrackPlan().
    async function getTrackPlan(trackName: string): Promise<TrackPlan> {
      assertSafeSlug(trackName);
      return fs.readTrackPlan(tracksDir, trackName);
    }
  • Helper: readTrackPlan() reads plan.md from disk and returns a TrackPlan object.
    async function readTrackPlan(tracksDir: string, trackName: string): Promise<TrackPlan> {
      const planPath = join(tracksDir, trackName, 'plan.md');
      const content = await readFile(planPath, 'utf8');
      return { trackName, content };
    }
Behavior3/5

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

Describes that it returns live file content, indicating a non-destructive read operation. No annotations exist, so description carries full burden, but lacks details on error handling or permissions for a mutation-free tool.

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?

Single sentence, front-loaded with key action and resource, no wasted words.

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?

Sufficient for a simple read tool with one parameter and no output schema; covers what the tool returns and what it is not, but could mention potential failure modes.

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 coverage is 0%, and description does not explain the 'trackName' parameter beyond its implied role in the purpose. Adds minimal meaning to 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?

Clearly states verb 'Read' and resource 'plan.md for a specific conductor track', distinguishing it from similar sibling tools like get_track_spec or get_track_index by emphasizing 'not docs, not memory'.

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?

Provides clear context that it returns live file content, differentiating from other file types, but does not explicitly state when to use or not use it, nor mention alternatives.

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