Bucky

Update project fields

updateProject

Idempotent

Patch project metadata (name, lifecycle status, externalRef). Pass projectId, or project with the name the user said; with neither, the result lists their projects and nothing is written. preview=true returns the field-level diff and writes nothing. A write returns a receipt; undoOperationId restores the captured prior fields. Does not archive or delete.

Input Schema

Name	Required	Description
`name`	No
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`preview`	No	When true, return the field-level diff and write nothing. Combined with undoOperationId, returns the stored receipt.
`project`	No	Project name to match, when you do not have the UUID. Case-insensitive; an exact name wins over a partial one. Matching more than one lists the candidates instead of guessing.
`projectId`	No	Project UUID. Omit if you pass `project`.
`externalRef`	No	Provenance of an imported project. Canonical form is `<system>:<id>` (e.g. `notion:<page-id>`). Unique per creator when set. Pass null to clear.
`lifecycleStatus`	No	Project stage. getProjectContext returns it as lifecycleStatus.
`undoOperationId`	No	Receipt id from a prior updateProject write. Restores the captured prior fields. With preview=true, inspects the receipt instead.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

changedInput schema / required

Previous value: -[
-  "preview",
-  "context"
-]New value: +[
+  "context"
+]

Changed2 schema fields changedOct 30, 2026

addedInput schema / properties / lifecycleStatus / description

Added value: +"Project stage. getProjectContext returns it as lifecycleStatus."

addedInput schema / properties / lifecycleStatus / enum

Added value: +[
+  "exploring",
+  "planning_budgeting",
+  "permits",
+  "ready_to_build",
+  "in_construction"
+]

Changed2 schema fields changedOct 26, 2026

removedInput schema / properties / llm_model

Removed value: -{
-  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "preview",
-  "context",
-  "llm_model"
-]New value: +[
+  "preview",
+  "context"
+]

Changed1 schema field changedOct 12, 2026

removedInput schema / properties / conversation_id

Removed value: -{
-  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
-  "type": "string"
-}

Changed4 schema fields changedSep 26, 2026

changedInput schema / properties / context / description

Previous value: -"Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\""New value: +"Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""

addedInput schema / properties / conversation_id

Added value: +{
+  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
+  "type": "string"
+}

addedInput schema / properties / llm_model

Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "preview",
-  "context"
-]New value: +[
+  "preview",
+  "context",
+  "llm_model"
+]

Changed3 schema fields changedSep 21, 2026

addedInput schema / properties / project

Added value: +{
+  "description": "Project name to match, when you do not have the UUID. Case-insensitive; an exact name wins over a partial one. Matching more than one lists the candidates instead of guessing.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / projectId / description

Added value: +"Project UUID. Omit if you pass `project`."

changedInput schema / required

Previous value: -[
-  "projectId",
-  "preview",
-  "context"
-]New value: +[
+  "preview",
+  "context"
+]

Changed1 schema field changedSep 15, 2026

addedInput schema / properties / externalRef

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 200,
+      "minLength": 1,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Provenance of an imported project. Canonical form is `<system>:<id>` (e.g. `notion:<page-id>`). Unique per creator when set. Pass null to clear."
+}

First observedSep 1, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already flag non-readonly, non-destructive, idempotent, open-world; the description adds real behavior beyond them: preview returns a field-level diff and writes nothing, a write returns a receipt, undoOperationId restores captured prior fields, and ambiguous name matches list candidates rather than guessing. That is exactly the mutation-safety context 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?

Four tight sentences, front-loaded with the patched fields, then identification rules, then preview/undo semantics. No filler and no repetition of schema text.

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

Completeness5/5

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

With eight parameters, no output schema, and a mutation entry point, the description still covers identification, dry-run, receipt/undo, and return shape ('a write returns a receipt'). Nothing an agent needs to call it correctly is missing.

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 description coverage is 88%, so the baseline is 3; the description additionally explains the projectId-vs-project decision, the preview-plus-undoOperationId interaction, and the no-identifier listing fallback. Minor gap: it does not say whether name/lifecycleStatus/externalRef are partial-patch optional or wholesale replacements.

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?

Names a specific verb and resource plus the exact patchable fields (name, lifecycleStatus, externalRef), and adds an explicit scope exclusion ('Does not archive or delete'). An agent can tell this apart from renameSavedFolder/deleteSavedFolder/saveToProject style siblings without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit routing rules: use `projectId`, or `project` with the spoken name, and states the fallback behavior when neither is supplied (lists projects, writes nothing). Also states preview=true and undoOperationId call conditions and the archive/delete exclusion.

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

All Bucky tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Update project fields

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources