Skip to main content
Glama

Bucky

by com.buckybuild
OverviewDiscussionsAdmin

List or unlist a project on the public map

setProjectMapListing
Idempotent

Put a project on the public Bucky map, or take it off. Pass projectId, or project with the name the user said; with neither, the result lists their projects and nothing is published. Listing publishes the build-lot centroid, the project name, its zone category, typology and lifecycle status to anyone — signed in or not. Nothing else about the project is published. The project must have a build lot with a centroid; a project that has only an address and no attached build parcel cannot be pinned. Ask the human before listing a site that is not already public knowledge. A client, a friend, or a private residence is theirs to publish, not yours. preview=true returns the current state, the exact pin that would be published, and any privacy warning, and writes nothing. Unlisting removes the pin but does not un-share anything already collected while it was public. To undo, call again with listed set to the opposite value (listed: false after listing); the result repeats this as undo.

Input Schema

NameRequiredDescriptionDefault
listedYestrue lists the project on the public map; false removes it. Listing publishes the build-lot centroid and the project name to anyone, signed in or not.
contextYesExplain 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."
previewNoWhen true, return the current listing state, the pin that would be published, and any privacy warning, and write nothing.
projectNoProject 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.
projectIdNoProject UUID. Omit if you pass `project`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "listed",
-  "preview",
-  "context"
-]New value: +[
+  "listed",
+  "context"
+]
  2. Changed2 schema fields changed
    • 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: -[
-  "listed",
-  "preview",
-  "context",
-  "llm_model"
-]New value: +[
+  "listed",
+  "preview",
+  "context"
+]
  3. Changed1 schema field changed
    • 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"
-}
  4. Changed4 schema fields changed
    • 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: -[
-  "listed",
-  "preview",
-  "context"
-]New value: +[
+  "listed",
+  "preview",
+  "context",
+  "llm_model"
+]
  5. Changed3 schema fields changed
    • 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",
-  "listed",
-  "preview",
-  "context"
-]New value: +[
+  "listed",
+  "preview",
+  "context"
+]
  6. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say openWorld and idempotent; the description goes well beyond them by naming the exact fields made public, the prerequisite (a build lot with a centroid, not address-only), and the asymmetry that unlisting 'does not un-share anything already collected while it was public.' That last point is a real irreversibility caveat an agent cannot get from destructiveHint=false.

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?

Front-loaded with the action, then scope, prerequisites, safety gate, and undo — a sensible order. It is dense rather than padded, though lines like 'A client, a friend, or a private residence is theirs to publish, not yours' spend words on tone that a shorter imperative could carry.

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 no output schema, the description still tells the agent what to expect back: preview returns current state, the exact pin, and privacy warnings; the result carries an `undo` field. Combined with the publish-set and undo semantics, an agent can invoke this correctly and interpret the response.

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 coverage is 100%, so baseline is 3, but the description adds semantics the schema lacks: the neither-identifier behavior (list projects, publish nothing) and the preview/write-nothing contract. It restates `project` and `projectId` matching rules already in the schema, which caps it below 5.

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?

States a concrete verb pair and resource ('Put a project on the public Bucky map, or take it off') that no sibling tool shares — none of the saved-folder, feasibility, or report tools touch public publication. It also defines the publishing scope (centroid, name, zone, typology, lifecycle) so an agent knows exactly what the operation changes.

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?

Explicit routing between `projectId` and `project`, an explicit no-identifier fallback ('with neither, the result lists their projects and nothing is published'), an explicit preview-first path, a human-approval gate for non-public sites, and an explicit undo path ('call again with `listed` set to the opposite value'). This is when-to-use and when-not guidance at a high standard.

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

All Bucky toolsInspect
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.

Resources