Skip to main content
Glama

Check a site: lot, zone and building envelope for an address

checkSite

Look up lot, zone, and building envelope for one street address in Canada or the US. Pass address. One address per call; cannot search or compare. Read exception before searching: its parcel zone label identifies the site-specific exception, chain contains the cited text and required references. Use that text first. text_missing means incomplete evidence, never no exception. Prevailing by-laws can be address-specific; do not apply every listed address provision to this lot. A live answer uses one site check from the monthly plan allowance; usage says if it was charged and how many are left. getBuckyMcpGuide reports the allowance for free. 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. Every envelope value carries a status. Never report not_extracted or site_specific_schedule as no limit or as zero — call explainFeasibilityStatus first. Envelope numbers are extracted ceilings. Call getBylawSection with a citation knowledgeSectionId, or with coverage.geoDivisionId, zone.code, and the section number, before treating a number as available on this lot. Do not fetch zone.bylawSourceUrl. lot.minLotFrontageM is the zone minimum. lot.lotConformity compares lot width, lot area, and floor area per unit to those minima. A missing input is unknown, never a pass. State every fail before quoting a unit count.

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": {
      "address": "<address>",
      "context": "<context>"
    },
    "name": "checkSite"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceNoWhich question the caller is answering. Used for attribution and to pick the link back; the payload is the same either way.full
addressYesStreet address to analyse, e.g. "4170 Sophia St, Vancouver BC".
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. Changed1 schema field changed
    • 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. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses billing behavior ('one site check from the monthly plan allowance'), analytics recording, how to interpret `usage`, how missing facts and `text_missing` should be treated, and multiple output-semantics caveats around envelope statuses and extracted ceilings. The readOnlyHint=false annotation is consistent with a lookup that consumes plan allowance and records analytics, so there is no contradiction.

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?

The description is dense and long, but the core purpose is front-loaded and nearly every sentence encodes a domain rule rather than filler. Structure could be improved with clearer grouping of the caveats, but the length is justified by the tool's complexity and lack of an output schema.

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 complex lookup with no output schema, the definition covers the important behavioral context: billing, citation requirements, status handling, missing-data interpretation, bylaw-section lookup dependencies, and the distinction between extracted ceilings and availability. An agent has enough information to avoid the main misuse patterns.

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?

Schema description coverage is 100%, so all four parameters are already documented in the schema. The description adds some address semantics ('one street address in Canada or the US', 'one address per call; cannot search or compare') but does not elaborate on `source`, `context`, or `conversation_id` beyond what the schema already says, 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 states a specific verb and resource: 'Look up lot, zone, and building envelope for one street address in Canada or the US.' It also scopes the tool to a single address and explicitly says it 'cannot search or compare,' separating it from broader search-style siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit sequencing and alternatives: read the exception before searching, use the exception text first, call explainFeasibilityStatus before treating certain statuses as no limit, call getBylawSection with a citation or zone/coverage identifiers, avoid fetching zone.bylawSourceUrl, and use getBuckyMcpGuide for free allowance checks. These are concrete when-to-use and when-not-to-use rules rather than implied guidance.

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.