Skip to main content
Glama

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 checkSite. Or pass geoDivisionId from coverage.geoDivisionId, zoneCode from zone.code, and sectionNumbers such as 3.1 or 3.2. Examples: {"sectionIds":[""]} or {"geoDivisionId":"<coverage.geoDivisionId>","zoneCode":"RM-4","sectionNumbers":["3.1"]}. sectionIds and sectionNumbers are arrays; do not pass address, city, sectionId or sectionNumber. The markdown is the schedule text. A number in the snapshot can still be conditional on frontage, tenure, or adjoining district. Each section returns at most 12,000 characters. A cut section has truncated: true, totalChars and nextOffset: call again with that section id and textOffset: nextOffset for the rest. Ids or section numbers with no active chunk come back in missing.

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

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.
zoneCodeNozone.code from checkSite, for example C-2.
sectionIdsNoCopy citations.*.knowledgeSectionId from checkSite. 1 to 4 ids.
textOffsetNoCharacter to start each section at. Default 0. Copy nextOffset from a truncated section to read the rest.
geoDivisionIdNocoverage.geoDivisionId from checkSite.
sectionNumbersNoSection numbers to read, for example 3.1 or 3.2. 1 to 4 numbers.
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. Changed3 schema fields changed
    • changedInput schema / properties / geoDivisionId / description
      Previous value: -"coverage.geoDivisionId from getFeasibilitySnapshot."New value: +"coverage.geoDivisionId from checkSite."
    • changedInput schema / properties / sectionIds / description
      Previous value: -"Copy citations.*.knowledgeSectionId from getFeasibilitySnapshot. 1 to 4 ids."New value: +"Copy citations.*.knowledgeSectionId from checkSite. 1 to 4 ids."
    • changedInput schema / properties / zoneCode / description
      Previous value: -"zone.code from getFeasibilitySnapshot, for example C-2."New value: +"zone.code from checkSite, for example C-2."
  4. Changed1 schema field changed
    • addedInput schema / properties / textOffset
      Added value: +{
      +  "description": "Character to start each section at. Default 0. Copy nextOffset from a truncated section to read the rest.",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  5. 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"
      +]
  6. 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"
      -}
  7. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: the 12,000-character cap per section, the truncated/totalChars/nextOffset continuation protocol, the `missing` return for inactive chunks, and the caveat that a cited number may still be conditional on frontage, tenure, or adjoining district.

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?

Front-loaded with the core action, then modes, then examples, then return behavior. Dense but nearly every sentence carries operational information; the two inline JSON examples add length that the prose already largely covers.

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 contract and does so well (markdown text, truncation fields, missing list). The only gap is that it does not say how the two input modes interact if both are supplied, or what happens when a section id is invalid versus merely missing.

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

Parameters5/5

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

Schema coverage is 100%, yet the description still adds real meaning: it maps sectionIds to citations.*.knowledgeSectionId, geoDivisionId to coverage.geoDivisionId, zoneCode to zone.code, gives sectionNumbers examples (3.1, 3.2), notes both are arrays, and explains textOffset as the nextOffset continuation value.

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 behind a snapshot citation') and ties itself to the checkSite citation flow, so an agent can distinguish it from checkSite or the feasibility tools without opening a schema.

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 modes (sectionIds from citations, or geoDivisionId+zoneCode+sectionNumbers) and names the source fields on checkSite. It also lists what not to pass (address, city, sectionId, sectionNumber), though it does not state when to prefer one mode over the other.

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.