Skip to main content
Glama

Create project update

create_project_update

Create a periodic project status update. Requires project_updates:write scope.

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_id": "<project_id>",
      "author_id": "<author_id>",
      "timeframe": "<timeframe>",
      "period_year": "<period_year>",
      "period_value": "<period_value>",
      "content": "<content>"
    },
    "name": "create_project_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoOptional custom title
contentYesUpdate content (required)
author_idYesAuthor Clerk user ID (required) - resolve via list_users
timeframeYesUpdate timeframe (required)
project_idYesProject ID (required) - resolve via list_projects
period_yearYesYear for this update period (required)
period_valueYesPeriod value - 1-12 for monthly, 1-4 for quarterly, etc. (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / author_id / description
      Previous value: -"Author Clerk user ID (required)"New value: +"Author Clerk user ID (required) - resolve via list_users"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project ID (required)"New value: +"Project ID (required) - resolve via list_projects"
  2. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / project_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  3. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  4. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / project_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  5. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare the write/idempotency/destructive profile, so the bar is lower. The description adds genuine value with the required scope (project_updates:write), but says nothing about duplicate handling for an existing timeframe/period combination, validation failures, or what the caller gets back — notable for a non-idempotent create.

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, permission requirement front-loaded after the purpose, no filler. It is efficient, though its brevity borders on under-specification rather than tightness.

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?

With 7 parameters (6 required), no output schema, and a timeframe/period scheme that has implicit coupling, the description should say more about how the period fields must agree and what a successful create returns. The scope note is helpful but leaves the caller dependent on the schema alone.

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 100%, including the helpful "resolve via list_users" and "resolve via list_projects" hints, so the schema carries all parameter meaning. The description adds no additional semantics for the required timeframe/period_year/period_value triple, which is where a caller is most likely to err.

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 uses a specific verb+resource ("Create a periodic project status update") that distinguishes it from generic create_* tools and from create_project_comment. It stops short of naming the update/get/delete siblings it pairs with, but the operation and object are unambiguous.

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?

No guidance on when to use this versus create_project_comment or update_project_update, and no preconditions beyond the scope string. The only actionable cue is the required scope, which is authorization, not context selection.

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