Skip to main content
Glama

Bucky

by com.buckybuild
OverviewDiscussionsAdmin

See what Bucky has mapped for a city

cityInventory
Read-onlyIdempotent

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. CMHC rental survey figures describe purpose-built rentals; the new-build proxy is the 2000 or later band. Missing facts are not surveyed or unavailable, never zero. Cite RMS figures as Source: CMHC, Rental Market Survey, October YYYY using referencePeriod. Cite starts and completions with their own source and period. If Bucky has not mapped the place, the result points to recording demand. It does not record demand by itself.

Input Schema

NameRequiredDescriptionDefault
latNo
lngNo
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."
cityNameNo
geoDivisionIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. 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"
-}
  3. Changed3 schema fields changed
    • removedInput schema / anyOf
      Removed value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "cityName": {
-        "maxLength": 100,
-        "minLength": 2,
-        "type": "string"
-      }
-    },
-    "required": [
-      "cityName"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "lat": {
-        "maximum": 90,
-        "minimum": -90,
-        "type": "number"
-      },
-      "lng": {
-        "maximum": 180,
-        "minimum": -180,
-        "type": "number"
-      }
-    },
-    "required": [
-      "lat",
-      "lng"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "geoDivisionId": {
-        "format": "uuid",
-        "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-        "type": "string"
-      }
-    },
-    "required": [
-      "geoDivisionId"
-    ],
-    "type": "object"
-  }
-]
    • addedInput schema / properties
      Added value: +{
+  "cityName": {
+    "maxLength": 100,
+    "minLength": 2,
+    "type": "string"
+  },
+  "context": {
+    "description": "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.\"",
+    "type": "string"
+  },
+  "conversation_id": {
+    "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"
+  },
+  "geoDivisionId": {
+    "format": "uuid",
+    "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+    "type": "string"
+  },
+  "lat": {
+    "maximum": 90,
+    "minimum": -90,
+    "type": "number"
+  },
+  "llm_model": {
+    "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"
+  },
+  "lng": {
+    "maximum": 180,
+    "minimum": -180,
+    "type": "number"
+  }
+}
    • addedInput schema / required
      Added value: +[
+  "context",
+  "llm_model"
+]
  4. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, yet the description still adds substantial behavior: the four coverage states in the response, the two-step disambiguation flow, the rule that missing facts mean "not surveyed or unavailable, never zero," the distinction between CMHC rental-survey figures and the 2000+ new-build proxy, and per-figure citation obligations with referencePeriod. None of that is recoverable from the annotations or schema.

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 argument-selection rules are correctly front-loaded, but the back half stacks citation boilerplate ("Cite RMS figures as Source: CMHC, Rental Market Survey, October YYYY...", "Cite starts and completions with their own source and period") that is formatting policy rather than tool-selection guidance. Every clause is defensible in isolation, yet the block runs long and mixes invocation rules with output-citation rules.

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 does the work of explaining returns: topic grouping, the four availability states, disambiguation behavior, and the fallback when a place is unmapped. That is enough for an agent to call it and interpret results. The residual gap is that the required `context` parameter and the semantics of `geoDivisionId` versus a name are only implied.

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 description coverage is only 20% (only `context` is documented), so the description must carry the load, and it largely does: it states the one-of constraint across cityName / lat+lng / geoDivisionId and the constraint that lat and lng travel together. It never mentions the required `context` analytics parameter, so it does not fully close a 0%-covered required field even though the schema covers that one.

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?

"Public city catalogue inventory" plus "Shows datasets grouped by topic as on file, not loaded yet, unavailable, or not confirmed" establishes the resource and the return shape concretely. The description then rules out adjacent scopes ("not lot feasibility or operator health"), which separates it from the feasibility siblings. It loses a point only because the opening noun phrase is jargon-ish and the verb has to be inferred from later sentences.

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?

The caller is told the three admissible input modes, the lat/lng pairing requirement, the "never pass a slug" exclusion, and the exact disambiguation loop (multiple matches → user picks → re-call with geoDivisionId). It also bounds the tool against feasibility and against the un-named "recording demand" tool. What is missing is a named sibling alternative; exclusions are stated by negation rather than by pointing at a specific tool.

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