Skip to main content
Glama

update_track_spec

Update technical decisions, architecture notes, or acceptance criteria by overwriting spec.md for an existing conductor track.

Instructions

Overwrite spec.md for an existing conductor track. Use to update technical decisions, architecture notes, or acceptance criteria.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
trackNameYes
contentYes

Implementation Reference

  • The core handler function `updateTrackSpec` that validates the slug, writes spec.md via the filesystem access layer, and returns the result.
    async function updateTrackSpec(trackName: string, content: string): Promise<UpdateTrackFileResult> {
      assertSafeSlug(trackName);
      await fs.writeTrackFile(tracksDir, trackName, 'spec.md', content);
      return { trackName, filename: 'spec.md', updated: true, length: content.length };
    }
  • Zod schema `UpdateTrackSpecSchema` defining the input shape with `trackName` and `content` (both required non-empty strings).
    export const UpdateTrackSpecSchema = z.object({
      trackName: z.string().min(1),
      content: z.string().min(1),
    });
  • Registration of the 'update_track_spec' tool on the MCP server, with its schema and the handler that delegates to ConductorManager.updateTrackSpec.
    server.tool(
      'update_track_spec',
      'Overwrite spec.md for an existing conductor track. Use to update technical decisions, architecture notes, or acceptance criteria.',
      UpdateTrackSpecSchema.shape,
      async (args) => {
        const result = await manager.updateTrackSpec(args.trackName, args.content);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(result, null, 2) }],
        };
      },
    );
  • Low-level filesystem helper `writeTrackFile` that writes spec.md to disk at the track's directory.
    async function writeTrackFile(tracksDir: string, trackName: string, filename: string, content: string): Promise<void> {
      const filePath = join(tracksDir, trackName, filename);
      await writeFile(filePath, content, { encoding: 'utf8' });
    }
  • src/index.ts:52-52 (registration)
    Top-level registration call that wires ConductorManager into the MCP server via registerConductorTools.
    registerConductorTools(server, conductorManager);
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states 'Overwrite' indicating mutation, but lacks details on side effects (e.g., whether it creates if missing, if content is appended or replaced, any requirements for existing track).

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, front-loaded with the main action ('Overwrite spec.md'), no redundant information. Every sentence adds value.

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?

Given two simple parameters and no output schema, the description is mostly adequate but lacks details on whether the track must exist, how errors are handled, and what the response contains. For a mutation tool, more context is needed.

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%, and the description adds no extra meaning beyond the parameter names. 'trackName' and 'content' are self-explanatory from the schema but the description does not elaborate on format, constraints, or purpose.

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?

The description clearly states the verb 'Overwrite' and the resource 'spec.md for an existing conductor track'. It differentiates from sibling tools like get_track_spec (read) and create_track (create track).

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?

The description provides explicit use cases: 'update technical decisions, architecture notes, or acceptance criteria.' It implies context but does not state when not to use or list 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