Skip to main content
Glama

project_update

Idempotent

Modify project details in Saga MCP's structured database by specifying fields to update, including status changes to archive projects.

Instructions

Update a project. Pass only the fields you want to change. Set status to "archived" to soft-delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProject ID
nameNo
descriptionNo
statusNo
tagsNo

Implementation Reference

  • The handler function that executes the 'project_update' logic, performing the database update and logging the activity.
    function handleProjectUpdate(args: Record<string, unknown>) {
      const db = getDb();
      const id = args.id as number;
    
      const oldRow = db.prepare('SELECT * FROM projects WHERE id = ?').get(id) as Record<string, unknown> | undefined;
      if (!oldRow) throw new Error(`Project ${id} not found`);
    
      const update = buildUpdate('projects', id, args, ['name', 'description', 'status', 'tags']);
      if (!update) throw new Error('No fields to update');
    
      const newRow = db.prepare(update.sql).get(...update.params) as Record<string, unknown>;
      logEntityUpdate(db, 'project', id, newRow.name as string, oldRow, newRow, ['name', 'status']);
    
      return newRow;
    }
  • The schema definition for the 'project_update' tool.
      name: 'project_update',
      description:
        'Update a project. Pass only the fields you want to change. Set status to "archived" to soft-delete.',
      annotations: { title: 'Update Project', readOnlyHint: false, destructiveHint: false, idempotentHint: true, openWorldHint: false },
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'integer', description: 'Project ID' },
          name: { type: 'string' },
          description: { type: 'string' },
          status: { type: 'string', enum: ['active', 'on_hold', 'completed', 'archived'] },
          tags: { type: 'array', items: { type: 'string' } },
        },
        required: ['id'],
      },
    },
  • Registration of the 'project_update' handler in the tools export.
    export const handlers: Record<string, ToolHandler> = {
      project_create: handleProjectCreate,
      project_list: handleProjectList,
      project_update: handleProjectUpdate,
Behavior4/5

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

The description adds valuable behavioral context beyond what annotations provide: it explains the partial update behavior ('Pass only the fields you want to change') and reveals that setting status to 'archived' performs a 'soft-delete' operation. The annotations already indicate this is a mutable (readOnlyHint: false), idempotent, non-destructive operation, but the description provides specific implementation details about update semantics and soft-deletion that aren't captured in annotations.

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 extremely concise with just two sentences that each provide essential information. The first sentence states the core purpose and a critical usage pattern, while the second explains a special case. There's zero wasted language, and the information is front-loaded effectively.

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 mutation tool with 5 parameters, 20% schema coverage, no output schema, and annotations that cover basic safety but not operational details, the description provides adequate but incomplete context. It explains update behavior and soft-deletion but doesn't cover error conditions, response format, permission requirements, or relationships to sibling tools. Given the complexity, more comprehensive guidance would be helpful.

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 only 20% schema description coverage (only the 'id' parameter has a description), the description compensates well by explaining the partial update approach and the special meaning of the 'status' parameter's 'archived' value. While it doesn't describe all 5 parameters individually, it provides crucial semantic context about how parameters should be used that goes beyond the bare 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 the action ('Update a project') and resource ('project'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'project_create' or 'task_update', which would require mentioning what specifically distinguishes project updates from other update operations.

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

Usage Guidelines3/5

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

The description provides some usage guidance by stating 'Pass only the fields you want to change' and explaining the special meaning of setting status to 'archived', which helps users understand how to use the tool. However, it doesn't explicitly state when to use this tool versus alternatives like 'project_create' or other update tools, nor does it mention prerequisites or context for when this tool is appropriate.

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/spranab/saga-mcp'

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