Skip to main content
Glama

save_project

Update an existing kanban project’s path, description, local folder, or archived status so project details stay current.

Instructions

Update a project: move to path, description, folder, archived. New projects are made by save_task with a new project path, so none is ever empty.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>"
    },
    "name": "save_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNonew path, like AI/hermes
folderNolocal repo dir; "" clears
projectYespath or id to update
archivedNo
descriptionNoone line

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses that the operation mutates an existing project and that new projects are not created here, but it does not describe permissions, reversibility, error behavior, or the implications of moving a project to a new path.

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 two sentences, front-loads the update action and fields, and avoids unnecessary wording. The second sentence efficiently clarifies the creation boundary with save_task.

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 without annotations or an output schema, the description is adequate but incomplete. It identifies the affected fields and the creation alternative, but leaves out important behavioral details such as permissions, side effects, and error handling.

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 80%, so the input schema already documents most parameters well. The description maps some fields to update actions but adds little semantic detail beyond what the schema provides, such as how path changes affect the project or what archived toggling entails.

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 states a specific verb and resource ('Update a project') and enumerates the updatable fields: path, description, folder, and archived. It also explicitly distinguishes creation from updating by naming save_task as the tool that creates new projects.

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 gives clear usage context by explaining that this tool updates existing projects while save_task creates new ones. It does not provide explicit when-not-to-use guidance beyond the creation/update distinction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.