Skip to main content
Glama

Coline

Write a project update

write_project_update

Writes a project update by hand (one line per line of text), or edits one with updateId. Edited updates say who edited them.

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>",
      "text": "<text>"
    },
    "name": "write_project_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
updateIdNo
projectIdYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
savedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent write, so the safety profile is covered. The description adds real behavior beyond that: edits record who edited them, and text is interpreted line by line. It omits permissions, whether repeated calls duplicate updates, and any failure modes.

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?

Two short sentences, with the primary create behavior front-loaded and the edit variant immediately after. Minor ambiguity in "one line per line of text", but no wasted wording.

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?

An output schema exists, so return values need no explanation, and the tool is a simple four-parameter mutation. Still missing are the meaning of "by hand", how projectId interacts with an edit, and any error or permission context, leaving modest gaps for a write tool.

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 coverage is only 25%, so the description must compensate; it does partially by explaining that updateId switches the call into edit mode, which the schema alone does not convey. Neither projectId nor text semantics (beyond the vague "one line per line of text") are clarified.

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 names a specific verb and resource ("Writes a project update") and distinguishes two modes: creating by hand versus editing when updateId is supplied. It stops short of differentiating itself from siblings like update_project or create_project, but the create-vs-edit split is stated plainly.

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?

It implies when to pick each mode (omit updateId to create, include it to edit), which is useful routing. There is no explicit guidance on when to use this versus update_project or when to prefer read_project_updates, and no prerequisites or exclusions are given.

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