Skip to main content
Glama

get_track_spec

Read the live technical specification (spec.md) for a conductor track by providing its track name.

Instructions

Read the spec.md for a specific conductor track. Returns the live technical specification.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
trackNameYes

Implementation Reference

  • Zod schema for the get_track_spec tool — validates a single required string parameter `trackName`.
    export const GetTrackSpecSchema = z.object({
      trackName: z.string().min(1),
    });
  • MCP tool registration and handler for 'get_track_spec'. Calls `manager.getTrackSpec(args.trackName)` and returns the file content as text.
    server.tool(
      'get_track_spec',
      'Read the spec.md for a specific conductor track. Returns the live technical specification.',
      GetTrackSpecSchema.shape,
      async (args) => {
        const file = await manager.getTrackSpec(args.trackName);
        return {
          content: [{ type: 'text' as const, text: file.content }],
        };
      },
    );
  • Registers the tool named 'get_track_spec' on the MCP server via `server.tool(...)` in the `registerConductorTools` function.
    server.tool(
      'get_track_spec',
      'Read the spec.md for a specific conductor track. Returns the live technical specification.',
      GetTrackSpecSchema.shape,
      async (args) => {
        const file = await manager.getTrackSpec(args.trackName);
        return {
          content: [{ type: 'text' as const, text: file.content }],
        };
      },
    );
  • Manager-level `getTrackSpec` function that validates the slug and delegates to `fs.readTrackFile(tracksDir, trackName, 'spec.md')`.
    async function getTrackSpec(trackName: string): Promise<TrackFile> {
      assertSafeSlug(trackName);
      return fs.readTrackFile(tracksDir, trackName, 'spec.md');
    }
  • Low-level `readTrackFile` helper that reads an arbitrary file from a track directory on disk and returns a `TrackFile` object.
    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 };
    }
Behavior2/5

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

No annotations provided, so description carries full burden. It indicates read-only behavior but lacks details on side effects, permissions, or error handling.

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, 15 words, front-loaded with essential information. No unnecessary text.

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 read tool with one parameter, description is adequate but sparse. Does not explain what a conductor track is or error scenarios, but sufficient given low complexity.

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 has 0% description coverage for parameter 'trackName'. Description adds minimal context by saying 'for a specific conductor track' but does not explain format or validation.

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?

Description clearly states the action (Read), resource (spec.md for a conductor track), and outcome (returns live technical specification). It distinguishes from siblings like update_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 explicit guidance on when to use this tool versus alternatives like update_track_spec or get_track_plan. Agent must infer from context.

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