Skip to main content
Glama

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.

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

Input Schema

NameRequiredDescriptionDefault
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.
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
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: -[
      -  "documentsLimit",
      -  "evidenceLimit",
      -  "include",
      -  "context"
      -]New value: +[
      +  "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: -[
      -  "documentsLimit",
      -  "evidenceLimit",
      -  "include",
      -  "context",
      -  "llm_model"
      -]New value: +[
      +  "documentsLimit",
      +  "evidenceLimit",
      +  "include",
      +  "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. 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"
      +]
  7. 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"
      +]
  8. 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`."
  9. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent and non-destructive, but the description adds real behavior beyond them: default include is empty so the payload is unchanged, per-list caps of 20/50, and a `truncation` object exposing total/returned/truncated for every cuttable list. The multi-match name resolution rule ('matching more than one lists the candidates instead of guessing') is exactly the kind of non-obvious behavior that prevents wrong invocation.

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?

Payload contents are front-loaded, followed by include behavior, limits, truncation and lookup strategy in a logical order. A couple of clauses duplicate the schema verbatim ('default is none, so the payload matches a call without include'; the CLI writes disclaimer), which is minor waste but not enough to obscure the content.

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?

With no output schema, the description carries the return-shape burden well by naming each section and the truncation contract. The one gap is that the required `context` analytics parameter, and the conversation_id tracking parameter, are never mentioned in the description, leaving the agent to discover a mandatory argument from the schema alone.

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 71%, and the description reinforces the highest-risk parameters: what `include` accepts, that limits default to 20 and cap at 50, that each include list returns up to 20, and the precedence of an exact `project` name over a partial one. Much of this restates the schema, so it adds value but not a great deal of new meaning.

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 first sentence names a specific verb (load) and enumerates exactly what the bundle contains: analysis envelope, agentStatus, document and evidence summaries, memory digest, external_ref. It also clarifies that tasks/members/insights/capital/visualEvidence are inlined sections rather than separate tools, which lets an agent distinguish this from the product-read siblings.

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 states when to call ('before composing reports or after scheduling analysis') and draws an explicit boundary against write paths ('Writes to those sections stay on the Bucky CLI'). It also explains the no-UUID path. It does not name the specific sibling tools it complements, so the routing is contextual rather than explicit.

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.