com.buckybuild/bucky

Est-ce que com.buckybuild/bucky est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.buckybuild/bucky » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 15 outils

• cityInventory≈ 580 tokens

  Public city catalogue inventory. Pass exactly one of: cityName, lat and lng together, or geoDivisionId. A city name with multiple matches returns choices; after the user chooses, call again with that candidate geoDivisionId. Never pass a slug. Shows datasets grouped by topic as on file, not loaded yet, unavailable, or not confirmed. This is city coverage, not lot feasibility or operator health. If Bucky has not mapped the place, the result points to recording demand. It does not record demand by itself.

  Paramètres, retour & exemple (6)

  Paramètres

  • lat · number · optionnel
  • lng · number · optionnel
  • context · string · requis
    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."
  • cityName · string · optionnel
  • llm_model · string · requis
    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.
  • geoDivisionId · string · optionnel

  Exemple d'appel

  {"name": "cityInventory", "arguments": {"context": "texte", "llm_model": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• explainFeasibilityStatus≈ 638 tokens

  Explain one Bucky coverage or per-fact provenance status and the safe next action. This is a pure static lookup: it does not inspect an address, retrieve property data, or call a database, geocoder, AI model, or third-party API. Accepts exactly one of: live, live_unavailable, planned_not_live, geo_division_uncatalogued, unseeded_place, geocode_failed, cited, cited_conditional, conditional_unresolved, no_limit_in_bylaw, not_extracted, site_specific_schedule, unverified_default, derived_from_cited, defaulted, missing. Copy the status verbatim from a feasibility result. An unknown status returns this list instead of failing.

  Paramètres, retour & exemple (3)

  Paramètres

  • status · string · requis · live | live_unavailable | planned_not_live | geo_division_uncatalogued | unseeded_place | geocode_failed | cited | cited_conditional
    A Bucky coverage resolution status or per-fact provenance status returned by a feasibility result. Copy it verbatim. Do not paraphrase or invent a status.
  • context · string · requis
    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."
  • llm_model · string · requis
    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.

  Exemple d'appel

  {"name": "explainFeasibilityStatus", "arguments": {"status": "live", "context": "texte", "llm_model": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• getBuckyMcpGuide≈ 492 tokens

  Call with no arguments on first contact. Optional `role`, `market`, and `scale` answer the first-call questions on a second call. Returns what this session should do next.

  Paramètres, retour & exemple (5)

  Paramètres

  • role · string · optionnel · developer | gc | reviewer
    Who is asking. Answers "Developer, GC, or municipal reviewer?".
  • scale · string · optionnel · single_parcel | portfolio
    One site or several. Answers "Single parcel, or a portfolio?".
  • market · string · optionnel · US | CA
    Which country the site is in. Answers "US or Canada?".
  • context · string · requis
    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."
  • llm_model · string · requis
    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.

  Exemple d'appel

  {"name": "getBuckyMcpGuide", "arguments": {"context": "texte", "llm_model": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• getBylawSection≈ 724 tokens

  Return the stored bylaw section text behind a snapshot citation. Pass `sectionIds` copied from `citations.*.knowledgeSectionId` on getFeasibilitySnapshot. Or pass `geoDivisionId` from `coverage.geoDivisionId`, `zoneCode` from `zone.code`, and `sectionNumbers` such as 3.1 or 3.2. The markdown is the schedule text. A number in the snapshot can still be conditional on frontage, tenure, or adjoining district. Ids or section numbers with no active chunk come back in `missing`.

  Paramètres, retour & exemple (6)

  Paramètres

  • context · string · requis
    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."
  • zoneCode · string · optionnel
    zone.code from getFeasibilitySnapshot, for example C-2.
  • llm_model · string · requis
    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.
  • sectionIds · array · optionnel
    Copy citations.*.knowledgeSectionId from getFeasibilitySnapshot. 1 to 4 ids.
  • geoDivisionId · string · optionnel
    coverage.geoDivisionId from getFeasibilitySnapshot.
  • sectionNumbers · array · optionnel
    Section numbers to read, for example 3.1 or 3.2. 1 to 4 numbers.

  Exemple d'appel

  {"name": "getBylawSection", "arguments": {"context": "texte", "llm_model": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• getFeasibilitySnapshot≈ 668 tokens

  Look up lot, zone, and building envelope for one street address in Canada or the US. Pass `address`. One address per call; cannot search or compare. Every envelope value carries a `status`. Never report `not_extracted` or `site_specific_schedule` as no limit or as zero — call `explainFeasibilityStatus` first. Envelope numbers are extracted ceilings. Call `getBylawSection` with a citation `knowledgeSectionId`, or with `coverage.geoDivisionId`, `zone.code`, and the section number, before treating a number as available on this lot. Do not fetch `zone.bylawSourceUrl`. `lot.minLotFrontageM` is the zone minimum. `lot.lotConformity` compares lot width, lot area, and floor area per unit to those minima. A missing input is `unknown`, never a pass. State every fail before quoting a unit count.

  Paramètres, retour & exemple (4)

  Paramètres

  • source · string · requis · zoning_lookup | lot_dimensions | setback_lookup | height_limit_lookup | lot_split_lookup | full
    Which question the caller is answering. Used for attribution and to pick the link back; the payload is the same either way.
  • address · string · requis
    Street address to analyse, e.g. "4170 Sophia St, Vancouver BC".
  • context · string · requis
    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."
  • llm_model · string · requis
    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.

  Exemple d'appel

  {"name": "getFeasibilitySnapshot", "arguments": {"source": "zoning_lookup", "address": "texte", "context": "texte", "llm_model": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• getProjectContext≈ 786 tokens

  Load one project with analysis envelope, compact agentStatus, document summaries, evidence summaries, the project memory digest, and external_ref when the project was imported from another system. Pass `include` for optional sections: tasks, members, insights, capital, visualEvidence. Default is none, so the payload stays the same as a call without include. Writes to those sections stay on the Bucky CLI. You do not need a UUID: pass `project` with the name the user said, or call with neither and the result lists their projects to choose from. Use before composing reports or after scheduling analysis.

  Paramètres, retour & exemple (7)

  Paramètres

  • context · string · requis
    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."
  • include · array · requis
    Optional extra sections. Default is none, so the payload matches a call without include. tasks, members, insights, capital, and visualEvidence each reuse the matching product read — they are not separate tools. Writes stay on the Bucky CLI.
  • project · string · optionnel
    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.
  • llm_model · string · requis
    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.
  • projectId · string · optionnel
    Project UUID. Omit if you pass `project`.
  • evidenceLimit · integer · requis
  • documentsLimit · integer · requis

  Exemple d'appel

  {"name": "getProjectContext", "arguments": {"context": "texte", "include": [], "llm_model": "texte", "evidenceLimit": 1, "documentsLimit": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• previewSiteCoverage≈ 531 tokens

  Free preview, no sign-in needed. For one street address in Canada or the US, it says whether Bucky covers the place and which zoning facts it holds for the lot (lot boundary, zone, height, density, setbacks, permitted uses, overlays, parking): found, partly on file, or not on file. It returns no values: no zone code, heights, setbacks or areas. The lot outline is a shape with no scale. Use it when the user is not signed in and asks what they can build at an address. For the numbers, call getFeasibilitySnapshot. That call asks the user to sign in.

  Paramètres, retour & exemple (3)

  Paramètres

  • address · string · requis
    Street address to analyse, e.g. "4170 Sophia St, Vancouver BC".
  • context · string · requis
    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."
  • llm_model · string · requis
    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.

  Exemple d'appel

  {"name": "previewSiteCoverage", "arguments": {"address": "texte", "context": "texte", "llm_model": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• produceProjectReport≈ 739 tokens

  Compose a project report PDF. Pass `projectId` or `project`; with neither, the result lists projects and no meter is spent. preview=true composes without spending. confirm=true exports, spends records.exports, and is irreversible. Returns a signed download URL, never PDF bytes.

  Paramètres, retour & exemple (10)

  Paramètres

  • detail · string · requis · brief | detailed
  • confirm · boolean · requis
    When true, compose (if needed), save, export PDF, and return a download URL. Required when preview is false. Spends records.exports and cannot be undone.
  • context · string · requis
    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 · boolean · requis
    When true, compose only — no export meter spend and no download URL.
  • project · string · optionnel
    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.
  • request · string · optionnel
  • audience · string · requis · investor | owner | board | resident
  • planName · string · optionnel
  • llm_model · string · requis
    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.
  • projectId · string · optionnel
    Project UUID. Omit if you pass `project`.

  Exemple d'appel

  {"name": "produceProjectReport", "arguments": {"detail": "brief", "confirm": true, "context": "texte", "preview": true, "audience": "investor", "llm_model": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• runFeasibilityAnalysis≈ 615 tokens

  Enqueue a fresh deterministic analysis run for a saved project. Pass `projectId`, or `project` with the name the user said; with neither, the result lists their projects and nothing is queued. Returns immediately with `agentStatus` (`queued`, `running`, `current`, `failed`, or `none`) and a receipt id; does not block on completion. Irreversible: a queued run cannot be un-queued from MCP. Re-check with `getProjectContext`, but no more than once every 15 seconds — it is a multi-query bundle, not a status endpoint.

  Paramètres, retour & exemple (4)

  Paramètres

  • context · string · requis
    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."
  • project · string · optionnel
    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.
  • llm_model · string · requis
    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.
  • projectId · string · optionnel
    Project UUID. Omit if you pass `project`.

  Exemple d'appel

  {"name": "runFeasibilityAnalysis", "arguments": {"context": "texte", "llm_model": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• saveToProject≈ 1334 tokens

  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.

  Paramètres, retour & exemple (17)

  Paramètres

  • lat · number · optionnel
    Latitude from getFeasibilitySnapshot. Supplied coordinates are never re-geocoded.
  • lng · number · optionnel
    Longitude from getFeasibilitySnapshot.
  • name · string · optionnel
  • role · string · optionnel · build | context
    build is the lot being developed; context is surrounding land. Default build.
  • action · string · requis · create | attach_reference | attach_parcels
    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 · string · optionnel
    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 · string · requis
    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 · object · optionnel
    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 · boolean · requis
    When true, return the field-level diff and write nothing.
  • project · string · optionnel
    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 · integer · optionnel
    Search half-width in metres when resolving parcel ids. Default 150.
  • llm_model · string · requis
    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.
  • projectId · string · optionnel
    Existing project UUID. Required by attach_parcels and attach_reference unless you pass `project`; ignored by create.
  • externalRef · string · optionnel
    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 · string · optionnel
  • idempotencyKey · string · optionnel
  • parcelExternalIds · array · optionnel
    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.

  Exemple d'appel

  {"name": "saveToProject", "arguments": {"action": "create", "context": "texte", "preview": true, "llm_model": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• screenLots≈ 3682 tokens

  Find the lots in one live Bucky city that match a buy box. Pass `city` or `geoDivisionId` with `thesis` (plain words), `criteria` (square feet, dollars), or both; or pass a saved `profileId`. Returns countOutcome (exact, partial, or unavailable), screeningRunId, and selected lots ranked largest first with a pass, fail, or not_available verdict per filter. totalMatches is a compatibility value and can be returned-page size when the total is unavailable. Report a not_available filter; never present the count as filtered by it. The execution preserves selection for optional candidate assessment; assessment candidate counts are separate from search totals. Each lot has `address` for getFeasibilitySnapshot and `parcelExternalId` for saveToProject. save=true saves the box (write scope) and returns a CSV link.

  Paramètres, retour & exemple (10)

  Paramètres

  • city · string · optionnel
    City as the user said it, e.g. "Laval" or "Bedford, MA". Omit when you pass geoDivisionId or profileId.
  • save · boolean · optionnel
    true saves the buy box to the account. Default false. Search execution history is recorded.
  • limit · integer · optionnel
    Lots to return. Default 10. countOutcome states whether the total is exact, partial, or unavailable.
  • thesis · string · optionnel
    The buy box in plain words, e.g. "industrial lots over half an acre outside the floodplain".
  • context · string · requis
    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."
  • criteria · object · optionnel
    Structured criteria. A field set here replaces the same field read from thesis.
  • saveName · string · optionnel
    Name for a saved box.
  • llm_model · string · requis
    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.
  • profileId · string · optionnel
    Saved buy box id. Runs the saved city and criteria. Do not combine with city, thesis, or criteria.
  • geoDivisionId · string · optionnel
    Division id, from an earlier screenLots or cityInventory result.

  Exemple d'appel

  {"name": "screenLots", "arguments": {"context": "texte", "llm_model": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• setProjectMapListing≈ 811 tokens

  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.

  Paramètres, retour & exemple (6)

  Paramètres

  • listed · boolean · requis
    true 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.
  • context · string · requis
    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 · boolean · requis
    When true, return the current listing state, the pin that would be published, and any privacy warning, and write nothing.
  • project · string · optionnel
    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.
  • llm_model · string · requis
    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.
  • projectId · string · optionnel
    Project UUID. Omit if you pass `project`.

  Exemple d'appel

  {"name": "setProjectMapListing", "arguments": {"listed": true, "context": "texte", "preview": true, "llm_model": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• submitBuckyFeedback≈ 565 tokens

  Open a human-reviewed feedback form and submit it to the Bucky product team. Call only when the user explicitly asks to send feedback, report a problem, suggest an improvement, or praise something. The server asks the MCP client to show the form; nothing is saved unless the human accepts it. Do not use for silent agent self-reporting.

  Paramètres, retour & exemple (4)

  Paramètres

  • context · string · requis
    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."
  • llm_model · string · requis
    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.
  • submissionId · string · optionnel
    Optional. A UUID for this submission; generated server-side when omitted. Pass the same UUID when retrying this exact feedback so it is not recorded twice.
  • affectedToolName · string · optionnel
    Tool the user is commenting on, when already known

  Exemple d'appel

  {"name": "submitBuckyFeedback", "arguments": {"context": "texte", "llm_model": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• uiGetAnalysisStatus≈ 434 tokens

  Return only the analysis `agentStatus` for a project. Cheap enough to poll. Used by the Bucky app view; the model should call getProjectContext instead.

  Paramètres, retour & exemple (3)

  Paramètres

  • context · string · requis
    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."
  • llm_model · string · requis
    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.
  • projectId · string · requis

  Exemple d'appel

  {"name": "uiGetAnalysisStatus", "arguments": {"context": "texte", "llm_model": "texte", "projectId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• updateProject≈ 804 tokens

  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.

  Paramètres, retour & exemple (9)

  Paramètres

  • name · string · optionnel
  • context · string · requis
    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 · boolean · requis
    When true, return the field-level diff and write nothing. Combined with undoOperationId, returns the stored receipt.
  • project · string · optionnel
    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.
  • llm_model · string · requis
    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.
  • projectId · string · optionnel
    Project UUID. Omit if you pass `project`.
  • externalRef · ? · optionnel
    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 · string · optionnel
  • undoOperationId · string · optionnel
    Receipt id from a prior updateProject write. Restores the captured prior fields. With preview=true, inspects the receipt instead.

  Exemple d'appel

  {"name": "updateProject", "arguments": {"context": "texte", "preview": true, "llm_model": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://buckybuild.com/api/mcp