Skip to main content
Glama

Canadian registered charities (CRA open data)

canada_registered_charities
Read-only

Search Canada Revenue Agency registered charities by year, province, city, designation, category, or keyword to verify registration, build non-profit prospect lists, or research the charity sector.

Instructions

Search Canada Revenue Agency registered charities (T3010 open data): business number, legal name, designation, category, city and province. Filter by filing year, province, city, designation, category code or keyword. Use it to verify a charity's registration, build non-profit prospect lists or research the charity sector. No directors or contact details. Runs the Apify Actor loudtzu/cra-charities on your own Apify account (pay per event: $0.003 per charity, billed by Apify; Apify platform usage may apply). Store page: https://apify.com/loudtzu/cra-charities

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity contains. Case-insensitive.
yearNoData year. T3010 open-data release year.2024
keywordNoName contains. Matches legal or account name.
maxItemsNoMax results. Stop after this many rows.
provinceNoProvince. 2-letter code, e.g. NS.
runOptionsNoOptional run limits (not passed to the Actor). maxTotalChargeUsd caps what this single call can cost you on Apify.
designationNoDesignation. Optional.
categoryCodeNoCategory code. CRA category code, e.g. 0140 (see CRA codes list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/destructive annotations it discloses the operational model: the run executes Actor loudtzu/cra-charities on the caller's own Apify account, with pay-per-event pricing of $0.003 per charity plus possible platform usage, and a store page for reference. It also bounds scope by excluding directors and contact data. Cost and account-auth disclosures are exactly the behavior an agent needs before invoking a metered scrape.

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?

Front-loaded with resource and fields, then filters, then use cases, then scope limits and pricing. Every sentence carries distinct information; nothing is redundant with the title.

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?

With no output schema, the description compensates by naming the returned fields (business number, legal name, designation, category, city, province). It also covers cost, execution venue and data exclusions, which are the main open questions for an 8-parameter, nested-schema, metered tool.

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, enum, default and the nested runOptions object is already documented. The description restates the filter set (filing year, province, city, designation, category code, keyword) without adding syntax or format detail, and never mentions maxItems or runOptions. Baseline 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?

States a specific verb ("Search") plus the exact resource (CRA registered charities, T3010 open data) and enumerates the fields returned and filterable. It is plainly distinguishable from siblings like canada_federal_corporations or canada_business_funding_finder without opening any schema.

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 three concrete use cases (registration verification, non-profit prospect lists, sector research) and a clear exclusion ("No directors or contact details"). It stops short of naming a sibling alternative for overlapping tasks, so 4 rather than 5.

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