bc_fire_perimeters_history

Look up historical wildfire perimeters from BC Wildfire Service's Fire Perimeters - Historical layer on DataBC, read live: by year or range of years, cause (lightning, person, unknown), minimum size in hectares, fire number, or a point (which recorded fire perimeters contain it), newest or largest first. Returns fire number, label, year, cause, size in hectares, fire date and how the perimeter was mapped. Attributes only, no boundary geometry. Years 1917 to 2025 as of the last read; a fire can have several polygons. Not current-season fires (use wildfire_status) and not every incident (use bc_fire_incidents_history).

Cost: 3 units of your allowance (see Rate limits).

ParametersCopy Anchor Link

• year (integer, optional): min 1900, max 2100
• year_from (integer, optional): min 1900, max 2100
• year_to (integer, optional): min 1900, max 2100
• cause (lightning, person, unknown, optional)
• min_hectares (number, optional): min 0, max 10000000
• fire_number (string, optional): min length 1, max length 60
• lat (number, optional): min 47.5, max 61
• lon (number, optional): min -140, max -113
• order (recent, largest, optional): default "recent"
• limit (integer, optional): min 1, max 50, default 20

RESTCopy Anchor Link

curl -X POST https://api.bcmcp.ca/v1/tools/bc_fire_perimeters_history \
  -H "Authorization: Bearer $BCDATA_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

MCPCopy Anchor Link

Call the tool bc_fire_perimeters_history with these arguments. Over raw JSON-RPC:

curl -X POST https://api.bcmcp.ca/mcp \
  -H "Authorization: Bearer $BCDATA_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"bc_fire_perimeters_history","arguments":{}}}'

What comes backCopy Anchor Link

Every answer is the same envelope, over REST and over MCP: available, data, citations, freshness and notes. See Citations and freshness.