Skip to main content
Glama

Canada Building Permits & Bid Signals (19 cities)

canada_building_permits
Read-only

Search issued Canadian building permits across 19 cities, filtered by date, value, permit type, work type and keyword, to find construction leads, contractor prospects and local development activity.

Instructions

Search issued building permits from 19 Canadian cities' official open data (including Toronto, Vancouver, Calgary, Edmonton, Winnipeg, Halifax, Mississauga, Kitchener, Waterloo, Victoria and Surrey), with optional Calgary/Edmonton planning and business-licence signals, federal contract awards and CanadaBuys open tenders. Filter by city or province, issue-date range, project value, permit type, work type, status and keyword. Use it to find construction leads, contractor and supplier prospects, or local development activity in Canada. Returns one clean JSON row per permit. Runs the Apify Actor loudtzu/canada-building-permits on your own Apify account (pay per event: $0.003 per permit row, billed by Apify; Apify platform usage may apply). Store page: https://apify.com/loudtzu/canada-building-permits

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "canada_building_permits"
  }
}

Input Schema

NameRequiredDescriptionDefault
citiesNoCities. Cities to query for building_permits when province is omitted. Setting province overrides this selection, including prefilled defaults. Opt-in calgary_* / edmonton_* sources are scoped by source selection: choosing them runs that feed even if this list omits the city, and does not add that city's building permits unless building_permits is also selected.
dateToNoIssued to (YYYY-MM-DD). Only permits issued on or before this date. For Delta this filters on the completion date.
statusNoStatus contains. Text match on permit status, e.g. Issued, Closed. Surrey and Edmonton have no status column and are skipped when you set this.
keywordNoKeyword. Searches each city's permit number and type/description-like fields.
signalsNoSignal types (opt-in). Optional nonempty type filter. Supplying this opts into common lead records, even for permits. With explicit sources (beyond the building_permits prefill alone), uses their intersection; without sources, selects every compatible feed (held feeds return diagnostics). Default permits-only output stays unchanged when signals is omitted and no extra sources are selected. tender_open selects canadabuys_open_tenders (federal open notices only; no provincial tenders). award selects ns_tender_awards (NS historical awarded public tenders); contract_award retains the existing fed…
sourcesNoSources (0.3 beta, opt-in). Opt-in source list. Prefill is building_permits for the Console form; there is no schema default, so cloud runs that omit sources keep permits-only unless signals is set. When signals is set and sources is omitted (or only the building_permits prefill), every compatible enabled feed for those signal types is selected — including held diagnostics. Explicit extra sources enable 0.3 signal mode. Selecting calgary_* or edmonton_* runs that city feed even if cities omits the city; it does not auto-add that city's building permits. Nine enabled extra sources, including H…
dateFromNoIssued from (YYYY-MM-DD). Only permits issued on or after this date. Leave empty for no lower limit. Delta publishes no issue date, so for Delta this filters on the completion date (the log warns). Opt-in sources use their event_date; federal data is first filtered to federalFiscalYears and then this bound is applied locally within its scan cap.
maxItemsNoMax permits in total. Total permits across all cities (default 100, up to 50,000). Split evenly between the cities you pick; a city that has fewer matches passes its unused share on to the next cities. In opt-in source mode this caps all saved signal rows, including permits, with a fair share per city/source task.
maxValueNoMaximum project value (CAD). Only permits with an estimated construction value at or below this. Permits with no value recorded (blank or 0) are left out. Delta and Winnipeg publish no value, so they are skipped when you set this.
minValueNoMinimum project value (CAD). Only permits with an estimated construction value at or above this. Permits with no value recorded (blank or 0) are left out when you set a value filter. Delta and Winnipeg publish no value, so they are skipped when you set this.
provinceNoProvince (optional). Query every covered municipality in this province. Overrides cities, including prefilled city defaults. Coverage is limited to the municipalities listed in the README.
workTypeNoWork type contains. Text match on work type, e.g. New, Addition, Alteration. Halifax accepts exactly: New Building, Addition, Renovation. Kingston, Victoria and Delta have no work-type column and are skipped when you set this.
permitTypeNoPermit type contains. Text match (contains, not case-sensitive) on the city's permit type. The words differ by city: see the README table. 'Residential' matches nothing in Oakville, Burlington, Kingston, Victoria, Surrey and Edmonton.
runOptionsNoOptional run limits (not passed to the Actor). maxTotalChargeUsd caps what this single call can cost you on Apify.
closingAfterNoTender closes after (YYYY-MM-DD). Strict YYYY-MM-DD lower bound for open-tender closing_date. Default when omitted: today in America/Halifax. Only future calendar days match — same-day deadlines are excluded even if the clock is still before the hour. Applies only to tender_open / canadabuys_open_tenders rows.
maxItemsPerCityNoMax permits per city (optional). Optional upper limit for each city, newest first. A city never gets more than this or its share of 'Max permits in total', whichever is smaller. In opt-in source mode, all source types in a city share this cap; national contracts have no inferred city.
includeAddressesNoInclude project site addresses. When false, project_address is null for every row. Addresses are only available from reviewed, enabled sources; see city provenance.
federalFiscalYearsNoFederal reporting fiscal years (optional). Federal contracts only. Omit for the current Canadian fiscal year (April–March), e.g. 2026-2027. Optionally select 1–3 consecutive-year labels such as ["2026-2027", "2025-2026"]. These filter reporting periods, not award dates; declared contracts C only. Results sort by contract_date descending WITHIN the hard scan cap (100 raw rows, 50/page, Crawl-delay 20s), not globally newest. dateFrom/dateTo/keyword/minValue/maxValue further filter event dates locally inside that cap; no automatic fallback to historical fiscal years. CKAN full-text q is unavaila…
refreshCanadaBuysCacheNoRefresh CanadaBuys tender cache. When true, force a fresh download of the CanadaBuys open-tenders CSV and overwrite today's entry in the named KV store cbp-canadabuys-cache (America/Halifax date key). Default false uses the daily cache when present. Useful for measuring cache-miss cost.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare read-only, open-world and non-destructive, and the description adds what they cannot: the workload runs on the caller's own Apify account as loudtzu/canada-building-permits, costs $0.003 per permit row billed by Apify with possible platform usage, and returns 'one clean JSON row per permit.' That billing/execution model is materially useful operational context.

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 and coverage, then filtering, then use cases, then cost and store link. The long parenthetical city list and store URL add length, but each sentence carries purpose, guidance, or pricing information rather than filler.

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?

For a 19-parameter tool with nested objects and no output schema, the description supplies the return shape ('one clean JSON row per permit'), cost model, and city/signal scope. The intricate source/signal interaction rules live in the schema, which is thorough, so nothing critical is missing, though the description does not itself warn that certain cities are skipped by certain filters.

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 every filter is documented in detail in the schema itself. The description only summarizes the filter dimensions ('city or province, issue-date range, project value, permit type, work type, status and keyword') without adding syntax or semantics beyond that — baseline 3 applies when the schema does the heavy lifting.

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+resource ('Search issued building permits') plus explicit scope (19 named Canadian cities, official open data) and the additional signal feeds. An agent can distinguish it immediately from the sibling Canada tools (charities, recalls, corporations, funding).

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 concrete use cases ('find construction leads, contractor and supplier prospects, or local development activity in Canada'), which is clear context for when this tool applies. It offers no exclusions or explicit routing to an alternative, though the sibling list contains no genuinely competing permits tool, so the gap is minor.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.