Skip to main content
Glama

update_prompts

Modify specific prompt fields like instructions or task prefixes in TaskFlow MCP's task management system without affecting other configuration settings.

Instructions

Update specific parts of the prompts configuration without replacing the entire object.

Use this to modify individual fields (instructions, taskPrefix, or taskSuffix) while keeping other settings unchanged.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instructionsNo
taskPrefixNo
taskSuffixNo

Implementation Reference

  • The tool handler function for 'update_prompts' which extracts the partial prompts from arguments and calls the TaskFlowService.updatePrompts method.
    async update_prompts(args: any) {
      const { instructions, taskPrefix, taskSuffix } = args ?? {};
      return service.updatePrompts({ instructions, taskPrefix, taskSuffix });
    },
  • Tool schema definition for 'update_prompts' including name, description, and input schema allowing optional updates to instructions, taskPrefix, or taskSuffix.
    export const UPDATE_PROMPTS_TOOL: Tool = {
      name: "update_prompts",
      description:
        "Update specific parts of the prompts configuration without replacing the entire object.\n\n" +
        "Use this to modify individual fields (instructions, taskPrefix, or taskSuffix) while keeping other settings unchanged.",
      inputSchema: {
        type: "object",
        properties: {
          instructions: { type: "string" },
          taskPrefix: { type: "string" },
          taskSuffix: { type: "string" },
        },
      },
    };
  • Registration of the 'update_prompts' tool (UPDATE_PROMPTS_TOOL) in the MCP server's list of available tools.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        PLAN_TASK_TOOL,
        GET_NEXT_TASK_TOOL,
        MARK_TASK_DONE_TOOL,
        OPEN_TASK_DETAILS_TOOL,
        LIST_REQUESTS_TOOL,
        ADD_TASKS_TO_REQUEST_TOOL,
        UPDATE_TASK_TOOL,
        DELETE_TASK_TOOL,
        ADD_SUBTASKS_TOOL,
        MARK_SUBTASK_DONE_TOOL,
        UPDATE_SUBTASK_TOOL,
        DELETE_SUBTASK_TOOL,
        EXPORT_TASK_STATUS_TOOL,
        ADD_NOTE_TOOL,
        UPDATE_NOTE_TOOL,
        DELETE_NOTE_TOOL,
        ADD_DEPENDENCY_TOOL,
        GET_PROMPTS_TOOL,
        SET_PROMPTS_TOOL,
        UPDATE_PROMPTS_TOOL,
        REMOVE_PROMPTS_TOOL,
        ARCHIVE_COMPLETED_REQUESTS_TOOL,
        LIST_ARCHIVED_REQUESTS_TOOL,
        RESTORE_ARCHIVED_REQUEST_TOOL,
      ],
    }));
  • Core implementation of prompts update logic in TaskFlowService, which updates only the provided prompt fields in the data file and persists changes.
    public async updatePrompts(updates: Partial<Prompts>) {
      await this.loadTasks();
      const now = new Date().toISOString();
      
      if (!this.data.prompts) {
        this.data.prompts = { createdAt: now };
      }
      
      // Update only provided fields
      if (updates.instructions !== undefined) this.data.prompts.instructions = updates.instructions;
      if (updates.taskPrefix !== undefined) this.data.prompts.taskPrefix = updates.taskPrefix;
      if (updates.taskSuffix !== undefined) this.data.prompts.taskSuffix = updates.taskSuffix;
      
      this.data.prompts.updatedAt = now;
      
      await this.saveTasks();
      
      return {
        status: "prompts_updated",
        prompts: this.data.prompts,
        message: "Prompts configuration has been updated."
      };
    }
Behavior3/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 discloses the tool's behavior as a partial update operation, which implies mutation but doesn't specify permissions, side effects, or response format. It adds some context (e.g., fields that can be modified) but lacks details on error handling or constraints, leaving gaps 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.

Conciseness5/5

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

The description is front-loaded with the core purpose in the first sentence, followed by usage guidance. Both sentences are essential, with no redundant information, making it efficiently structured and appropriately sized for the tool's complexity.

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 no annotations, 0% schema coverage, no output schema, and a mutation tool with 3 parameters, the description is incomplete. It covers the purpose and usage well but lacks behavioral details (e.g., permissions, side effects) and parameter specifics, making it adequate but with clear gaps for safe agent invocation.

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

Parameters4/5

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

With 0% schema description coverage and 3 parameters, the description compensates by listing the specific fields that can be updated ('instructions, taskPrefix, or taskSuffix'), providing meaningful semantics beyond the bare schema. However, it doesn't detail the format or constraints of these fields, so it doesn't fully cover all parameter aspects.

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 specific action ('Update specific parts of the prompts configuration') and resource ('prompts configuration'), distinguishing it from sibling tools like 'set_prompts' (which likely replaces the entire object) and 'get_prompts' (which reads). It explicitly mentions the partial update nature versus full replacement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool ('to modify individual fields... while keeping other settings unchanged') and implies when not to use it (e.g., use 'set_prompts' for full replacement or 'get_prompts' for reading). It clearly differentiates from alternatives like 'set_prompts' by specifying partial updates.

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/pinkpixel-dev/taskflow-mcp'

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