Skip to main content
Glama

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.

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": {
      "listed": "<listed>",
      "context": "<context>"
    },
    "name": "setProjectMapListing"
  }
}

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.
contextYesA few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other personal details.
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`.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / context / description
      Previous 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.\""New value: +"A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as \"a customer\". Do not quote the user or include names, emails, or other personal details."
  3. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
      -  "listed",
      -  "preview",
      -  "context"
      -]New value: +[
      +  "listed",
      +  "context"
      +]
  4. 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"
      +]
  5. 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"
      -}
  6. 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"
      +]
  7. 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"
      +]
  8. Added

TDQS

A4.6/5.0
Behavior4/5

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

Goes well past the annotations: it enumerates exactly what becomes public (build-lot centroid, project name, zone category, typology, lifecycle status) and states "Nothing else about the project is published." It also discloses a hard prerequisite (a build lot with a centroid), the irreversibility caveat for unlisting, and a consent norm — none of which the annotations convey. The one gap is that it never frames the operation as a state change with side effects beyond the pin itself, which the destructiveHint=false/readOnlyHint=false pairing leaves slightly ambiguous.

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 identifiers, then publication scope, then safety, then preview/undo — a sensible order with no filler sentences. It runs long for one paragraph, but nearly every sentence carries a distinct operational or safety fact. A light edit could merge the identifier and preview sentences for tighter flow.

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?

There is no output schema, so the description must describe returns — and it does: preview yields current state, the exact pin, and any privacy warning; ambiguous name matching yields candidates; the normal result echoes an `undo` value. For a 6-parameter, open-world, publishing tool, an agent has everything needed to call it safely 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 the schema already carries the per-parameter detail, including the case-insensitive name matching rule. The description still adds interaction semantics the schema cannot express: supplying neither identifier puts the tool into list-only mode, and toggling `listed` to the opposite value is the documented undo. That is real added meaning rather than restatement.

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?

Opens with a specific verb pair and resource: "Put a project on the public Bucky map, or take it off." That immediately separates it from siblings like updateProject or saveToProject, which also touch projects but do not publish them. The scope (public visibility) is stated in the first sentence.

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: pass `projectId`, or `project` with the name the user said; nothing supplied means list-only and no publication. It also names the preview path, the consent precondition ("Ask the human before listing a site that is not already public knowledge"), and the undo path via the opposite `listed` value. The only thing absent is a named sibling alternative, which the guidance itself makes unnecessary.

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.