Skip to main content
Glama

Canada federal corporations (Corporations Canada open data)

canada_federal_corporations
Read-only

Search and filter official Corporations Canada federal corporation records by province, status, date, or name for KYC checks, lead lists, and market sizing.

Instructions

Search federally incorporated Canadian corporations from the official Corporations Canada dataset on open.canada.ca (updated daily): corporation number, business number, names, governing act, status, incorporation date, last annual filing, city and province. Filter by province, active/inactive status, incorporation date range or name keyword. Use it for KYC-style lookups, new-company lead lists or market sizing. Street addresses are removed. Runs the Apify Actor loudtzu/canada-federal-corporations on your own Apify account (pay per event: $0.003 per corporation, billed by Apify; Apify platform usage may apply). Store page: https://apify.com/loudtzu/canada-federal-corporations

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_federal_corporations"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoStatus contains. Case-insensitive match on status or status detail, e.g. 'Dissolved', 'Amalgamated', 'Dissolution Pending'.
fetchAllNoFetch all matches (up to 50,000). Ignore Max corporations and return every match, capped at 50,000 per run. Use filters to stay under the cap.
maxItemsNoMax corporations. Stop after this many matches (default 100, maximum 50,000).
provinceNoProvince/territory. Province of the registered office.any
runOptionsNoOptional run limits (not passed to the Actor). maxTotalChargeUsd caps what this single call can cost you on Apify.
nameKeywordNoName contains. Case-insensitive match on the English or French corporate name.
statusGroupNoActive or inactive. Which source files to read.active
includeNonCbcaNoInclude non-CBCA corporations. Also include not-for-profits, boards of trade, co-operatives etc. (default: only Canada Business Corporations Act companies).
incorporatedToNoIncorporated on/before (YYYY-MM-DD). Optional end date.
flagIndividualsNoFlag names that may be individuals. Adds nameMayBeIndividual (true/false). True for professional corporations ('.. Professional Corporation', 'Dr. ..', '.. MD Inc.', '.. Personal Real Estate Corporation') and names that start with (or, in French names, follow 'Gestion', 'Les Entreprises' etc. with) a given name and a surname, e.g. 'John Smith Holdings Inc.', 'Paige Thompson Photography Inc.'. Heuristic only.
incorporatedFromNoIncorporated on/after (YYYY-MM-DD). Based on the anniversary (incorporation/amalgamation) date.
redactIndividualsNoBlank names that may be individuals. On by default. Replaces flagged corporate names (name and nameAlt) with '[redacted: may be an individual]' (about 2.7% of active corporations). The corporation number, business number and url are kept, so you can still look the record up. Turn off to get every name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, open-world behavior, but the description adds material context beyond them: pay-per-event pricing ($0.003 per corporation, Apify platform usage may apply), runs on the caller's own Apify account, street addresses removed, and a 50,000-row cap. It does not explain pagination or how results are delivered (dataset items vs. synchronous payload), which is the main remaining behavioral gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense paragraph, front-loaded with what the tool searches and where the data comes from, followed by filters, use cases, caveats, pricing, and store link in descending priority. No sentence is filler; even the privacy and pricing notes earn their place for an agent deciding whether to call.

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 12 parameters, nested runOptions, and no output schema, the description compensates well by enumerating the returned fields and disclosing cost, cap, and default redaction. It is nearly complete for a paid, external-actor-backed search tool, missing only how results are returned and whether empty matches cost anything.

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 coverage is 100%, so every parameter including the nested runOptions and the redaction/flagging flags is already documented in structured form; the description only summarizes the filter set ('province, active/inactive status, incorporation date range or name keyword'). It adds no syntax, defaults, or interactions beyond what the schema states, so the baseline 3 applies.

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 ('Search federally incorporated Canadian corporations') and pins the source dataset (Corporations Canada on open.canada.ca, updated daily), then enumerates the returned fields. An agent can distinguish this from the sibling Canada datasets (permits, charities, recalls, funding) purely from the description.

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 ('KYC-style lookups, new-company lead lists or market sizing') and lists the available filter axes, which tells the agent when this tool is the right fit. It stops short of explicit exclusions or naming an alternative tool for adjacent needs (e.g. charities or funding data).

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