Skip to main content
Glama

Bucky

by com.buckybuild
OverviewDiscussionsAdmin

Explain a Bucky feasibility status

explainFeasibilityStatus
Read-onlyIdempotent

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYesA Bucky coverage resolution status or per-fact provenance status returned by a feasibility result. Copy it verbatim. Do not paraphrase or invent a status.
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."
llm_modelYesThe 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.
conversation_idNoEcho 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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 / properties / status / description
      Previous value: -"A Bucky coverage resolution status or per-fact provenance status returned by a feasibility result. Must be copied verbatim from a feasibility result — 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. Do not paraphrase or invent a status."New value: +"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."
    • changedInput schema / required
      Previous value: -[
-  "status",
-  "context"
-]New value: +[
+  "status",
+  "context",
+  "llm_model"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / status / description
      Previous value: -"A Bucky coverage resolution status or per-fact provenance status returned by a feasibility result. Must be copied verbatim from a feasibility result — 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. Do not paraphrase or invent a status."New value: +"A Bucky coverage resolution status or per-fact provenance status returned by a feasibility result. Must be copied verbatim from a feasibility result — 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. Do not paraphrase or invent a status."
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "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"
-]New value: +[
+  "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"
+]
  3. Changed2 schema fields changed
    • changedInput schema / properties / status / description
      Previous value: -"A Bucky coverage resolution status or per-fact provenance status returned by a feasibility result."New value: +"A Bucky coverage resolution status or per-fact provenance status returned by a feasibility result. Must be copied verbatim from a feasibility result — 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. Do not paraphrase or invent a status."
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "live",
-  "live_unavailable",
-  "planned_not_live",
-  "geo_division_uncatalogued",
-  "unseeded_place",
-  "geocode_failed",
-  "cited",
-  "cited_conditional",
-  "conditional_unresolved",
-  "no_limit_in_bylaw",
-  "not_extracted",
-  "unverified_default"
-]New value: +[
+  "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"
+]
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint: true, idempotentHint: true, destructiveHint: false, and openWorldHint: false, covering safety. The description adds non-obvious behavior beyond these annotations: it is a 'pure static lookup' making no external calls, and critically, 'an unknown status returns this list instead of failing'. This error-handling detail and the explicit absence of side effects are valuable and go beyond what annotations convey.

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

Conciseness5/5

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

The description is compact and efficiently structured. It front-loads the core purpose in the first sentence, clarifies the non-behavior in the second, lists all valid inputs in the third, and closes with the error behavior. Every sentence earns its place; even the long enum list is necessary for correctness. No redundant or filler sentences exist.

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 static lookup tool with rich annotations and 100% schema coverage, this description is complete. It states the purpose, the exact valid inputs, the copying instruction, the lack of external calls, and the behavior for unknown statuses. Since there is no output schema, the description's phrase 'Explain ... and the safe next action' adequately hints at the return value. Nothing an agent needs to invoke it correctly is missing.

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

Parameters3/5

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

The input schema has 100% description coverage: each parameter (status, context, llm_model, conversation_id) is fully documented with detailed descriptions including enum values, length constraints, and privacy instructions. The tool description mainly reinforces the 'copy verbatim' instruction for the status parameter, which is already present in the schema. With such complete schema coverage, the description adds no meaning beyond the schema, so the baseline of 3 is appropriate.

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 opens with a specific verb and resource: 'Explain one Bucky coverage or per-fact provenance status' and adds 'and the safe next action'. It explicitly says 'pure static lookup' and lists what it does NOT do (address inspection, property data, database, geocoder, AI, third-party API), which sharply distinguishes it from siblings like runFeasibilityAnalysis or getBuckyMcpGuide. The enumeration of accepted inputs leaves no ambiguity about scope.

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 description provides clear usage context by stating it is a static lookup and instructing to 'Copy the status verbatim from a feasibility result', which tells the agent exactly how to obtain the input. It also hints at when to use this tool (when an explanation of a status is needed) versus others that perform analysis. However, it never names sibling tools or gives explicit conditions for when NOT to use this tool, so routing guidance is implied rather than stated.

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