Skip to main content
Glama

Bucky

by com.buckybuild
OverviewDiscussionsAdmin

Get project context bundle

getProjectContext
Read-onlyIdempotent

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. Documents and evidence return up to documentsLimit / evidenceLimit (default 20, max 50); each include list returns up to 20. truncation gives total, returned and truncated for every list that can be cut. 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.

Input Schema

NameRequiredDescriptionDefault
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."
includeNoOptional 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.
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`.
evidenceLimitNo
documentsLimitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "documentsLimit",
-  "evidenceLimit",
-  "include",
-  "context"
-]New value: +[
+  "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: -[
-  "documentsLimit",
-  "evidenceLimit",
-  "include",
-  "context",
-  "llm_model"
-]New value: +[
+  "documentsLimit",
+  "evidenceLimit",
+  "include",
+  "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. Changed2 schema fields changed
    • addedInput schema / properties / include
      Added value: +{
+  "default": [],
+  "description": "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.",
+  "items": {
+    "enum": [
+      "tasks",
+      "members",
+      "insights",
+      "capital",
+      "visualEvidence"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / required
      Previous value: -[
-  "documentsLimit",
-  "evidenceLimit",
-  "context",
-  "llm_model"
-]New value: +[
+  "documentsLimit",
+  "evidenceLimit",
+  "include",
+  "context",
+  "llm_model"
+]
  5. 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: -[
-  "documentsLimit",
-  "evidenceLimit",
-  "context"
-]New value: +[
+  "documentsLimit",
+  "evidenceLimit",
+  "context",
+  "llm_model"
+]
  6. Changed2 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"
+}
    • changedInput schema / properties / projectId / description
      Previous value: -"Project UUID to load. Omit to have the user pick from their projects."New value: +"Project UUID. Omit if you pass `project`."
  7. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), it discloses default include=none, per-list return caps with defaults and maxima, that truncation metadata (`total`, `returned`, `truncated`) is supplied for every cuttable list, that ambiguous project names return candidates instead of guessing, and that writes are out of scope. This is exactly the behavioral context the annotations cannot carry.

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?

It is front-loaded with what is loaded, then moves through optional sections, limits, truncation, and the UUID-free path in a logical order with no filler. It is dense but every sentence carries actionable information; the sentence about writes staying on the CLI is the only mild repetition with the `include` schema description.

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?

For a six-parameter read tool with no output schema, the description adequately conveys both input behavior (include, limits, project resolution) and output shape (envelope sections, truncation metadata), so an agent can call it and interpret the response without additional docs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67% and the two numeric limits have no schema descriptions at all, so the description does real work: it states their default of 20 and max of 50, notes each include list returns up to 20, and explains project-name matching semantics (case-insensitive, exact beats partial, ambiguity lists candidates). The `include` optionality and payload-equivalence with an omitted include are also clarified.

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?

The description names a specific verb and resource ('Load one project') and enumerates the exact contents of the bundle (analysis envelope, agentStatus, document/evidence summaries, memory digest, external_ref). It is clearly distinguishable from siblings like produceProjectReport or uiGetAnalysisStatus, which generate output or report status rather than loading a project context bundle.

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

Usage Guidelines4/5

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

It gives concrete timing guidance ('Use before composing reports or after scheduling analysis') and points write operations to the Bucky CLI, which implicitly scopes this tool to reads. It also explains the no-UUID path (pass `project`, or call with neither to list projects). It stops short of naming a specific sibling to prefer for a given alternative scenario.

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