Skip to main content
Glama

Bucky

by com.buckybuild
OverviewDiscussionsAdmin

Get cited bylaw section text

getBylawSection
Read-onlyIdempotent

Return the stored bylaw section text behind a snapshot citation. Pass sectionIds copied from citations.*.knowledgeSectionId on getFeasibilitySnapshot. Or pass geoDivisionId from coverage.geoDivisionId, zoneCode from zone.code, and sectionNumbers such as 3.1 or 3.2. The markdown is the schedule text. A number in the snapshot can still be conditional on frontage, tenure, or adjoining district. Ids or section numbers with no active chunk come back in missing.

Input Schema

TableJSON 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."
zoneCodeNozone.code from getFeasibilitySnapshot, for example C-2.
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.
sectionIdsNoCopy citations.*.knowledgeSectionId from getFeasibilitySnapshot. 1 to 4 ids.
geoDivisionIdNocoverage.geoDivisionId from getFeasibilitySnapshot.
sectionNumbersNoSection numbers to read, for example 3.1 or 3.2. 1 to 4 numbers.
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. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds real behavioral context beyond them: the returned content is markdown schedule text, cited numbers may be conditional on frontage/tenure/adjoining district, and unresolvable ids/section numbers surface in a `missing` field.

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?

Five tight sentences, front-loaded with what is returned and then the two lookup routes. Every sentence carries distinct information — source paths, return format, the conditional caveat, and the `missing` behavior — with no filler.

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 7-parameter, two-mode lookup tool with no output schema, the description covers the return shape (markdown text plus a `missing` field), the alternative input routes, and the semantic caveat about conditional numbers. The plumbing parameters (context, llm_model, conversation_id) are self-documented in the schema.

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 100%, so the baseline is 3, but the description adds meaning the schema does not: it identifies the exact source paths for `sectionIds`, `geoDivisionId`, and `zoneCode`, gives examples like 3.1/3.2 for `sectionNumbers`, and frames the uuid group versus the geo/zone/numbers group as alternatives.

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?

States a specific verb and resource ('Return the stored bylaw section text') and ties it to a concrete upstream source ('behind a snapshot citation'). This clearly distinguishes it from getFeasibilitySnapshot, which produces the citations it consumes.

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?

Gives two explicit invocation paths: either pass `sectionIds` copied from getFeasibilitySnapshot's citations, or pass the geoDivisionId/zoneCode/sectionNumbers trio. It does not state whether the two paths can be combined or what happens if neither matches, so the 'when-not' case is left implicit.

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