Skip to main content
Glama

update-phase

Update an existing phase's details such as name, dates, status, budget, notes, color, and billing by providing the phase ID and optional fields.

Instructions

Update an existing phase

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
phase_idYesThe phase ID (phase_id)
project_idNoThe ID of the project this phase belongs to
nameNoPhase name
start_dateNoPhase start date (YYYY-MM-DD)
end_dateNoPhase end date (YYYY-MM-DD)
statusNoPhase status (0=Draft, 1=Tentative, 2=Confirmed)
notesNoPhase notes and description
non_billableNoNon-billable flag (0=billable, 1=non-billable)
colorNoPhase color (hex code)
default_hourly_rateNoDefault hourly rate for this phase
budget_totalNoTotal budget for this phase
activeNoActive status (1=active, 0=archived)

Implementation Reference

  • The main handler function for the 'update-phase' tool. It destructures phase_id from params, passes the rest as updateData to floatApi.patch(), and returns the updated phase.
    // Update phase
    export const updatePhase = createTool(
      'update-phase',
      'Update an existing phase',
      z.object({
        phase_id: z.union([z.string(), z.number()]).describe('The phase ID (phase_id)'),
        project_id: z.number().optional().describe('The ID of the project this phase belongs to'),
        name: z.string().optional().describe('Phase name'),
        start_date: z.string().optional().describe('Phase start date (YYYY-MM-DD)'),
        end_date: z.string().optional().describe('Phase end date (YYYY-MM-DD)'),
        status: z.number().optional().describe('Phase status (0=Draft, 1=Tentative, 2=Confirmed)'),
        notes: z.string().optional().describe('Phase notes and description'),
        non_billable: z.number().optional().describe('Non-billable flag (0=billable, 1=non-billable)'),
        color: z.string().optional().describe('Phase color (hex code)'),
        default_hourly_rate: z.string().optional().describe('Default hourly rate for this phase'),
        budget_total: z.number().optional().describe('Total budget for this phase'),
        active: z.number().optional().describe('Active status (1=active, 0=archived)'),
      }),
      async (params) => {
        const { phase_id, ...updateData } = params;
        const phase = await floatApi.patch(`/phases/${phase_id}`, updateData, phaseSchema);
        return phase;
      }
    );
  • The Zod input schema for the update-phase tool, defining all optional updateable fields (project_id, name, start_date, end_date, status, notes, non_billable, color, default_hourly_rate, budget_total, active) plus the required phase_id.
    z.object({
      phase_id: z.union([z.string(), z.number()]).describe('The phase ID (phase_id)'),
      project_id: z.number().optional().describe('The ID of the project this phase belongs to'),
      name: z.string().optional().describe('Phase name'),
      start_date: z.string().optional().describe('Phase start date (YYYY-MM-DD)'),
      end_date: z.string().optional().describe('Phase end date (YYYY-MM-DD)'),
      status: z.number().optional().describe('Phase status (0=Draft, 1=Tentative, 2=Confirmed)'),
      notes: z.string().optional().describe('Phase notes and description'),
      non_billable: z.number().optional().describe('Non-billable flag (0=billable, 1=non-billable)'),
      color: z.string().optional().describe('Phase color (hex code)'),
      default_hourly_rate: z.string().optional().describe('Default hourly rate for this phase'),
      budget_total: z.number().optional().describe('Total budget for this phase'),
      active: z.number().optional().describe('Active status (1=active, 0=archived)'),
    }),
  • The 'updatePhase' export is imported from './project-management/phases.js' and included in the legacyTools array at line 251, registering it as an available MCP tool.
    createPhase,
    updatePhase,
  • The patch() method on the FloatApi service that the update-phase handler calls internally to make the HTTP PATCH request to the Float API.
    async patch<T>(
      url: string,
      data: unknown,
      schema?: z.ZodType<T>,
      format: ResponseFormat = 'json'
    ): Promise<T> {
      return this.handleRateLimitRetry(() => this.makeRequest<T>('PATCH', url, data, schema, format));
    }
  • The phaseSchema Zod schema used to validate the response from the Float API after an update-phase call.
    export const phaseSchema = z.object({
      phase_id: z.number().optional(), // Float API uses phase_id, not id
      project_id: z.number(),
      name: z.string(),
      start_date: z.string().nullable().optional(),
      end_date: z.string().nullable().optional(),
      status: z.number().optional(), // 0 = Draft, 1 = Tentative, 2 = Confirmed
      notes: z.string().nullable().optional(),
      non_billable: z.number().nullable().optional(), // 0 = billable, 1 = non-billable
      color: z.string().nullable().optional(),
      default_hourly_rate: z.string().nullable().optional(), // String per API docs
      budget_total: z.number().nullable().optional(),
      created: z.string().nullable().optional(), // Float API uses 'created', not 'created_at'
      modified: z.string().nullable().optional(), // Float API uses 'modified', not 'updated_at'
      active: z.number().nullable().optional(), // 0 = archived, 1 = active
    });
Behavior1/5

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

No annotations provided, so description carries full burden. It only says 'Update an existing phase' with no disclosure of side effects (e.g., partial update behavior, permission requirements, what happens if phase not found, or whether it returns the updated phase). This is insufficient for a mutation tool.

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

Conciseness3/5

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

The description is extremely short (5 words), which is concise but sacrifices necessary detail. It is front-loaded but misses critical context about usage and behavior. A 3 reflects minimum viability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 12 parameters, no annotations, and no output schema, the description is vastly incomplete. It fails to explain what the tool returns, validation behavior, or how to handle errors. Far below the level needed for effective agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed descriptions for each parameter (e.g., start_date format, status values, non_billable flag). The description adds no extra meaning beyond what the schema already provides, so baseline 3 is appropriate.

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?

Description states 'Update an existing phase' which clearly identifies the action on a specific resource. While it does not differentiate from sibling tools like create-phase or delete-phase, the name itself implies mutation, so purpose is clear.

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 on when to use this tool versus alternatives such as create-phase or get-phase. Missing prerequisites like requiring the phase_id, or that only provided fields will be updated. The description is silent on usage 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/asachs01/float-mcp'

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