Skip to main content
Glama

sitekick_project_update

DestructiveIdempotent

Update the project using its expected revision and complete blueprint.

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": {
      "payload": "<payload>",
      "site_ref": "<site_ref>",
      "idempotency_key": "<idempotency_key>",
      "expected_revision": "<expected_revision>"
    },
    "name": "sitekick_project_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
site_refYes
idempotency_keyYes
expected_revisionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds two genuinely useful behavioral facts — the update is a whole-document replacement ("complete blueprint") and it is revision-guarded ("expected revision") — but says nothing about what a revision mismatch returns or how idempotency_key deduplicates replays.

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 short sentence with no filler; the revision and payload concepts lead. It is efficient, though efficiency here shades into under-specification given the schema's complexity.

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?

This is a destructive, revision-guarded mutation over a large nested payload with two mutually exclusive shapes, yet the description covers only one of them and omits idempotency and site scoping. An output schema exists so return values need not be explained, but the input contract is left far too thin.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description has to compensate and largely fails: it hints at expected_revision and the blueprint half of payload but never explains site_ref, idempotency_key, or the native_campaign alternative branch of the payload oneOf. With four required parameters and a deeply nested schema, this is a significant gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb and resource ("Update the project"), which is clear enough at a glance. However, it reduces the payload to "complete blueprint" when the schema accepts either a blueprint or a native_campaign variant, so an agent reading only the description gets a partial picture of what can be updated.

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 guidance on when to use this versus sitekick_project_create, sitekick_project_seal, or sitekick_project_estimate, and no mention of the optimistic-concurrency preconditions implied by expected_revision. The agent must infer the workflow entirely from parameter names.

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