Skip to main content
Glama
jakedx6

Helios-9 MCP Server

by jakedx6

update_initiative

Update initiative details including name, objective, status, priority, dates, and metadata to keep project information current.

Instructions

Update initiative details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
initiative_idYesThe unique identifier of the initiative to update
nameNoNew name for the initiative
objectiveNoNew objective
descriptionNoNew description
statusNoNew status
priorityNoNew priority
owner_idNoNew owner ID
start_dateNoNew start date
target_dateNoNew target date
metadataNoNew metadata
tagsNoNew tags

Implementation Reference

  • The main handler function for the update_initiative tool. Calls UpdateInitiativeSchema.parse to validate args, logs the update, calls supabaseService.updateInitiative() to perform the update, and returns the updated initiative with a success message.
    export const updateInitiative = requireAuth(async (args: any) => {
      const { initiative_id, ...updates } = UpdateInitiativeSchema.parse(args)
      
      logger.info('Updating initiative', { initiative_id, updates })
      
      const initiative = await supabaseService.updateInitiative(initiative_id, updates)
      
      logger.info('Initiative updated successfully', { initiative_id: initiative.id })
      
      return {
        initiative,
        message: `Initiative "${initiative.name}" updated successfully`
      }
    })
  • Zod schema for update_initiative input validation. Requires initiative_id (UUID) and allows optional fields: name, objective, description, status, priority, owner_id, start_date, target_date, metadata, tags.
    const UpdateInitiativeSchema = z.object({
      initiative_id: z.string().uuid(),
      name: z.string().min(1).max(255).optional(),
      objective: z.string().min(1).optional(),
      description: z.string().optional(),
      status: z.enum(['planning', 'active', 'on_hold', 'completed', 'cancelled']).optional(),
      priority: z.enum(['critical', 'high', 'medium', 'low']).optional(),
      owner_id: z.string().uuid().optional(),
      start_date: z.string().datetime().optional(),
      target_date: z.string().datetime().optional(),
      metadata: z.object({}).optional(),
      tags: z.array(z.string()).optional()
    })
  • Tool registration object (updateInitiativeTool) with name 'update_initiative', description, and JSON Schema input schema defining all optional/required properties for the tool.
    export const updateInitiativeTool: MCPTool = {
      name: 'update_initiative',
      description: 'Update initiative details',
      inputSchema: {
        type: 'object',
        properties: {
          initiative_id: {
            type: 'string',
            format: 'uuid',
            description: 'The unique identifier of the initiative to update'
          },
          name: {
            type: 'string',
            minLength: 1,
            maxLength: 255,
            description: 'New name for the initiative'
          },
          objective: {
            type: 'string',
            minLength: 1,
            description: 'New objective'
          },
          description: {
            type: 'string',
            description: 'New description'
          },
          status: {
            type: 'string',
            enum: ['planning', 'active', 'on_hold', 'completed', 'cancelled'],
            description: 'New status'
          },
          priority: {
            type: 'string',
            enum: ['critical', 'high', 'medium', 'low'],
            description: 'New priority'
          },
          owner_id: {
            type: 'string',
            format: 'uuid',
            description: 'New owner ID'
          },
          start_date: {
            type: 'string',
            format: 'date-time',
            description: 'New start date'
          },
          target_date: {
            type: 'string',
            format: 'date-time',
            description: 'New target date'
          },
          metadata: {
            type: 'object',
            description: 'New metadata'
          },
          tags: {
            type: 'array',
            items: {
              type: 'string'
            },
            description: 'New tags'
          }
        },
        required: ['initiative_id']
      }
    }
  • Handler registration mapping the string 'update_initiative' to the updateInitiative handler function in the initiativeHandlers export object.
    export const initiativeHandlers = {
      list_initiatives: listInitiatives,
      get_initiative: getInitiative,
      create_initiative: createInitiative,
      update_initiative: updateInitiative,
  • The helper API client method updateInitiative that makes a PATCH request to /api/mcp/initiatives/{initiativeId} with the partial update data.
    async updateInitiative(initiativeId: string, updates: Partial<Initiative>): Promise<Initiative> {
      const response = await this.request<{ initiative: Initiative }>(`/api/mcp/initiatives/${initiativeId}`, {
        method: 'PATCH',
        body: JSON.stringify(updates),
      })
      
      return response.initiative
    }
Behavior2/5

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

No annotations are present, and the description omits behavioral traits such as whether the update is a partial or full replacement, permissions required, or side effects. For a mutation tool, this is a significant gap.

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

Conciseness2/5

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

The description is extremely short (three words), which is under-specified for a tool with 11 parameters and no annotations. It lacks front-loaded essential information.

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 the tool's complexity (11 parameters, no output schema, no annotations, mutation operation), the description fails to provide necessary context like return value, error conditions, or update semantics. It is completely inadequate.

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 description coverage is 100%, and each parameter already has a clear description. The tool's description adds no additional semantic value beyond what is in the schema.

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 'Update initiative details', indicating a write operation on an existing initiative. This distinguishes it from create_initiative and get_initiative, but doesn't elaborate on what 'details' means beyond what the schema shows.

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 siblings like create_initiative or list_initiatives. It lacks information on prerequisites, success conditions, or when not to use it.

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/jakedx6/helios9-MCP-Server'

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