Skip to main content
Glama

Coline

Change a project

update_project
Destructive

Changes a project's name, outcome, state, lead, dates or whether its weekly update posts to its channel.

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": {
      "workspace": "<workspace>",
      "projectId": "<projectId>"
    },
    "name": "update_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
stateNo
outcomeNoThe outcome in one line.
projectIdYes
startDateNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
leadUserIdNo
targetDateNo
postUpdatesToChannelNo

Output Schema

NameRequiredDescriptionDefault
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the description needed to explain what makes this destructive — yet it says nothing about partial-update behavior, whether passing null to leadUserId/startDate/targetDate clears the value, or whether omitted fields are preserved. For a mutating tool with three nullable parameters, the clearing semantics are the single most important behavior and they are absent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

A single front-loaded sentence with no filler; every word carries content. The field list reads as a run-on enumeration rather than grouped clauses, but nothing is wasted.

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

Completeness2/5

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

With 9 parameters, 22% schema description coverage, nullable fields, a destructive-hint mutation, and only one enum documented, the definition is under-specified for the complexity. An output schema exists so return values need no explanation, but the mutation semantics and nullable-clearing behavior should still be covered.

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?

The field enumeration roughly maps to the schema properties (name, outcome, state, leadUserId, startDate, targetDate, postUpdatesToChannel), but schema description coverage is only 22%, and the description adds no format or semantic detail — no date format despite maxLength-40 strings with no format constraint, no explanation of state transitions, no null-clearing semantics. It restates property names rather than adding meaning.

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 opens with a specific verb and resource ("Changes a project's") and enumerates the mutable fields, so an agent can distinguish it from create_project, delete_project, and read_project. It stops short of naming siblings explicitly, which keeps it from a 5.

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

Usage Guidelines2/5

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

There is no statement of when to prefer this over read_project or write_project_update, no mention of prerequisites (e.g. lead must be a workspace member), and no guidance on whether unspecified fields are left untouched. The agent must infer partial-update semantics entirely.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources