Skip to main content
Glama

update_project

Idempotent

Change a project's title or description while preserving unspecified fields. Only the main token can update Casefile projects; each changed field files an audit entry.

Instructions

Changes a project's title and description; a field left out stays. Only a main token edits projects. The key never changes. Each changed field files a field_changed entry with the previous and the new value in the project's case; a value equal to the current one files nothing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesProject key, case-insensitive. An unknown key is refused with `project_not_found`
titleNoNew title; when left out, the title stays
descriptionNoNew description, up to 320 characters after trimming (`project_description_too_long` otherwise); when left out, the description stays

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.2

TDQS

A4.7/5.0
Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations: partial-update semantics, the requirement for a `main` token, the key never changing, event-log entries with previous/new values, and no-op behavior when values are unchanged. These are exactly the non-obvious traits an agent needs to predict side effects.

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?

Three sentences, each carrying necessary information: the core action, the authorization constraint, and the event-log side effects. Important behavioral facts are front-loaded before lower-level details.

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

Completeness5/5

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

For a three-parameter tool with a full output schema, rich annotations, and schema descriptions for all parameters, the description covers the remaining behavioral essentials: authorization, partial updates, immutability of the key, and event recording. Nothing needed for correct invocation is missing.

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?

Schema coverage is 100%, so the baseline is 3. The description adds extra meaning by explaining that omitted fields stay unchanged, equal values file no event, and the key is immutable — details beyond the schema's property descriptions and examples.

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 names a specific verb ('Changes'), a specific resource ('a project'), and the exact fields affected ('title and description'). This clearly distinguishes update_project from sibling tools like update_task and update_participant without needing to inspect schemas.

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 makes it clear this tool is for editing project title and description, which is sufficient context for selecting it. It does not explicitly name alternatives or exclusion conditions, but the resource and field specificity separate it from siblings.

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