Skip to main content
Glama

Get the Bucky MCP guide

getBuckyMcpGuide
Read-onlyIdempotent

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, and the two ideas Bucky uses: lists, and the properties in them. Signed in, it also returns profile: the standing answers Bucky has for this user and the questions still open; save answers with updateMyProfile.

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": "getBuckyMcpGuide"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoWho is asking. Answers "Developer, GC, or municipal reviewer?".
scaleNoOne site or several. Answers "Single parcel, or a portfolio?".
marketNoWhich country the site is in. Answers "US or Canada?".
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.
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. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • 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. 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: -[
      -  "context",
      -  "llm_model"
      -]New value: +[
      +  "context"
      +]
  4. 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"
      -}
  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: -[
      -  "context"
      -]New value: +[
      +  "context",
      +  "llm_model"
      +]
  6. Changed3 schema fields changed
    • addedInput schema / properties / market
      Added value: +{
      +  "description": "Which country the site is in. Answers \"US or Canada?\".",
      +  "enum": [
      +    "US",
      +    "CA"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / role
      Added value: +{
      +  "description": "Who is asking. Answers \"Developer, GC, or municipal reviewer?\".",
      +  "enum": [
      +    "developer",
      +    "gc",
      +    "reviewer"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / scale
      Added value: +{
      +  "description": "One site or several. Answers \"Single parcel, or a portfolio?\".",
      +  "enum": [
      +    "single_parcel",
      +    "portfolio"
      +  ],
      +  "type": "string"
      +}
  7. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false, and openWorldHint false, so safety behavior is covered. The description adds useful state-dependent behavior — signed-in sessions also return `profile`, and it reports which questions are still open. It does not describe size, format, or stability of the returned guide, so it adds moderate rather than rich context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening instruction is correctly front-loaded, and the sentences are packed with routing and return information. But phrasing such as "the two ideas Bucky uses: lists, and the properties in them" and "what this session should do next" is elliptical and costs more parsing than it should for a five-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 must convey what comes back, and it does describe three return elements (next steps, the lists/properties concept, and profile when signed in). However, it omits any mention of the required `context` parameter and its privacy constraint, and it does not explain the relationship between the guide payload and the profile payload, leaving an agent to guess how much content to expect.

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

Parameters2/5

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

The schema already carries 100% description coverage, so the baseline would be 3; however, the description's instruction to "call with no arguments on first contact" conflicts with the schema's required `context` parameter, actively misleading the agent. It adds useful sequencing meaning for role/market/scale (they answer the first-call questions) but never mentions `context` or `conversation_id`, the two parameters the schema flags as analytics-critical.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete deliverable — "returns what this session should do next, and the two ideas Bucky uses: lists, and the properties in them" — so the agent knows this is an orientation/onboarding tool rather than a data tool. It falls short of a clean verb+resource statement of the guide's scope and never says plainly that it is a usage guide for this server, which the title implies but the body never states.

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 explicit timing ("Call with no arguments on first contact") and sequences the optional role/market/scale answers to a second call. It also routes the follow-up action to a named different tool, "save answers with updateMyProfile", which is real when-and-where guidance. The only weakness is that no when-not-to-call condition is stated.

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.