BC Data docs

laws_section

Text of one section of an act or regulation

The current text of a section as BC Laws publishes it. With as_of, it looks for the text recorded in the source's Point in Time change records. Those records hold the text before an amendment only for some amendments, so an as_of answer is either a recorded pre-amendment text with its effective date, or an explicit statement that the source offers none. BC Laws offers no consolidation for an arbitrary date.

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

Parameters

  • doc_id (string, required)
  • section (string, required): min length 1, max length 20
  • as_of (string, optional)

REST

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

MCP

Call the tool laws_section 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":"laws_section","arguments":{"doc_id":"...","section":"..."}}}'

What comes back

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

On this page