Bucky

Create or attach to a project

saveToProject

Create a project (create), attach lots (attach_parcels), or attach a knowledge reference (attach_reference). Pass projectId or project; with neither, the result lists projects and writes nothing. For attach_parcels, pass a WGS84 GeoJSON polygon (up to 500 selected parcels), or copy lot.parcelExternalId from getFeasibilitySnapshot. Polygon cannot be combined with parcelExternalIds or radiusM. Results report source truncation and attached count. preview=true returns the diff and writes nothing. A write returns a receipt. Not reversible on this surface.

Input Schema

Name	Required	Description
`lat`	No	Latitude from getFeasibilitySnapshot. Supplied coordinates are never re-geocoded.
`lng`	No	Longitude from getFeasibilitySnapshot.
`name`	No
`role`	No	build is the lot being developed; context is surrounding land. Default build.
`action`	Yes	create: new project from a site. attach_parcels: attach lots to an existing project (use lot.parcelExternalId from getFeasibilitySnapshot). attach_reference: link a knowledge section to an existing project.
`address`	No	Street address of the site. On `create` this is geocoded server-side when lat/lng are not supplied, and is what gets recorded as the project address.
`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."
`polygon`	No	WGS84 GeoJSON Polygon for attach_parcels. Attach the parcels selected by the product area flow, up to 500. Interior rings exclude parcels. Use polygon instead of parcelExternalIds and radiusM. Maximum 512 coordinates.
`preview`	No	When true, return the field-level diff and write nothing.
`project`	No	Project name to match instead of a UUID, for attach_parcels and attach_reference. Matching more than one lists the candidates instead of guessing. Ignored by create.
`radiusM`	No	Search half-width in metres when resolving parcel ids. Default 150.
`projectId`	No	Existing project UUID. Required by attach_parcels and attach_reference unless you pass `project`; ignored by create.
`externalRef`	No	Provenance of an imported project. Canonical form is `<system>:<id>` (e.g. `notion:<page-id>`). Unique per creator when set. Returned on getProjectContext. Distinct from idempotencyKey.
`sectionUuid`	No
`idempotencyKey`	No
`parcelExternalIds`	No	Source parcel ids to attach. Copy lot.parcelExternalId from getFeasibilitySnapshot. If they are not in the current area, pass a larger radiusM on attach_parcels.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 31, 2026
- removedInput schema / properties / polygon / additionalProperties
```
Removed value: -false
```
- changedInput schema / required
```
Previous value: -[
-  "action",
-  "preview",
-  "context"
-]New value: +[
+  "action",
+  "context"
+]
```

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: -[
-  "action",
-  "preview",
-  "context",
-  "llm_model"
-]New value: +[
+  "action",
+  "preview",
+  "context"
+]

Changed2 schema fields 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"
-}

addedInput schema / properties / polygon

Added value: +{
+  "additionalProperties": false,
+  "description": "WGS84 GeoJSON Polygon for attach_parcels. Attach the parcels selected by the product area flow, up to 500. Interior rings exclude parcels. Use polygon instead of parcelExternalIds and radiusM. Maximum 512 coordinates.",
+  "properties": {
+    "coordinates": {
+      "items": {
+        "items": {
+          "items": {
+            "type": "number"
+          },
+          "maxItems": 2,
+          "minItems": 2,
+          "type": "array"
+        },
+        "maxItems": 512,
+        "minItems": 4,
+        "type": "array"
+      },
+      "maxItems": 128,
+      "minItems": 1,
+      "type": "array"
+    },
+    "type": {
+      "const": "Polygon",
+      "type": "string"
+    }
+  },
+  "required": [
+    "type",
+    "coordinates"
+  ],
+  "type": "object"
+}

Changed5 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 / properties / parcelExternalIds / description

Previous value: -"Source parcel ids to attach. Copy lot.parcelExternalId from getFeasibilitySnapshot, or from bucky parcels search."New value: +"Source parcel ids to attach. Copy lot.parcelExternalId from getFeasibilitySnapshot. If they are not in the current area, pass a larger radiusM on attach_parcels."

changedInput schema / required

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

Changed2 schema fields changedSep 21, 2026

addedInput schema / properties / project

Added value: +{
+  "description": "Project name to match instead of a UUID, for attach_parcels and attach_reference. Matching more than one lists the candidates instead of guessing. Ignored by create.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / projectId / description

Added value: +"Existing project UUID. Required by attach_parcels and attach_reference unless you pass `project`; ignored by create."

Changed4 schema fields changedSep 15, 2026

addedInput schema / properties / address / description

Added value: +"Street address of the site. On `create` this is geocoded server-side when lat/lng are not supplied, and is what gets recorded as the project address."

addedInput schema / properties / externalRef

Added value: +{
+  "description": "Provenance of an imported project. Canonical form is `<system>:<id>` (e.g. `notion:<page-id>`). Unique per creator when set. Returned on getProjectContext. Distinct from idempotencyKey.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / lat / description

Added value: +"Latitude from getFeasibilitySnapshot. Supplied coordinates are never re-geocoded."

addedInput schema / properties / lng / description

Added value: +"Longitude from getFeasibilitySnapshot."

First observedSep 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish readOnly=false, destructive=false, idempotent=false, openWorld=true, but the description adds real value beyond them: preview returns a field-level diff and writes nothing, a write returns a receipt, results report source truncation and attached count, and changes are not reversible on this surface. The 'not reversible' caveat sits in mild tension with destructiveHint=false without quite contradicting it (attaching parcels adds rather than destroys data). Permission or auth requirements and failure modes are not disclosed.

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?

Dense and front-loaded: the action enum and ID routing come first, then mode-specific constraints, then preview and return behavior. Every sentence carries facts, though the middle section packs polygon, parcelExternalIds, radiusM, truncation, preview, and receipts into a single run-on stretch that is harder to scan than the opening.

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

Completeness4/5

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

For a 16-parameter mutation with no output schema, the description covers the critical call paths and return signals (diff, receipt, attached count, truncation). Remaining gaps are per-action parameter applicability and error behavior, which for openWorld=true calls an agent would want spelled out.

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?

With 81% schema coverage the schema carries most of the load, but the description still adds meaning: polygon vs parcelExternalIds vs radiusM are explicitly exclusive, the 500-parcel selection cap is stated, and parcelExternalIds are sourced from lot.parcelExternalId on getFeasibilitySnapshot. It does not explain which of the sixteen parameters belong to which action (name, address, externalRef, sectionUuid, idempotencyKey are left to the schema).

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 immediately names the three concrete operations (create, attach_parcels, attach_reference) and what each touches, so the agent knows exactly what resource is being acted on. It falls short of a 5 because it never distinguishes itself from the write-side siblings (updateProject, createSavedFolder), leaving the agent to infer boundary cases such as modifying an existing project.

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?

It gives explicit routing rules: pass projectId or project, and with neither the call degrades to listing projects and writing nothing. It also names mutually exclusive parameter combinations (polygon cannot be combined with parcelExternalIds or radiusM) and offers preview=true as the non-writing alternative. This is when/when-not guidance with alternatives, not just context.

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.

Create or attach to a project

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources