Skip to main content
Glama
Cafelatte1

FronyBoard

by Cafelatte1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

update_project

Change a project's name, description, repository, or status while preserving its key and leaving roadmap, periods, and tasks untouched. Use to rename, pause, or archive projects.

Instructions

Use it when the user renames, re-describes, pauses or archives a project.

Update a project's own fields — pass at least one of name, description, repo, status.
The key (and with it the task id prefix) never changes, and nothing here touches the
roadmap, periods or tasks. `name` and `description` follow create_project's language rule.

`status`: active | paused | archived. paused only changes the badge; archived hides the
project from list_projects and refuses every other mutation until it is set back to
active. Archived is as far as removal goes — there is no hard delete.

Input Schema

NameRequiredDescriptionDefault
keyYes
nameNo
repoNo
statusNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it explains the key (and task id prefix) is immutable, that paused only changes a badge, that archived hides the project from list_projects and blocks every other mutation until reverted, and that there is no hard delete — exactly the side-effect details an agent needs.

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?

Front-loaded with the usage trigger, then the constraint, then per-field semantics. Short declarative sentences, no filler, and the most consequential fact (archived blocks mutations) is stated plainly.

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

Completeness4/5

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

For a five-parameter mutation tool with no annotations and no output schema, this covers triggers, preconditions, field semantics and irreversibility. The only real omission is what repo accepts or how it is validated.

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 0%, so the description must compensate and largely does: it enumerates the permissible status values with their semantics, marks key as immutable, and points name/description at create_project's language rule. The repo parameter is only listed, never explained, leaving one gap.

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?

States a specific verb and resource ('Update a project's own fields') and immediately bounds the scope by naming what it does not touch (roadmap, periods, tasks), which separates it from update_task, upsert_milestone and set_overview.

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 opening sentence gives concrete triggers: renames, re-describes, pauses or archives. It also enforces a precondition ('pass at least one of name, description, repo, status'). It stops short of naming an alternative tool for cases like hard removal, though it does say no hard delete exists.

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

Deploy Server

Other Tools