Equibles

Canadian Regulatory Filings (SEDAR+)

GetCanadianFilings

Read-only

List the documents a company listed in Canada filed on SEDAR+, the Canadian securities regulators' filing system, for the issuer of one Canadian listing written MIC:TICKER (e.g. XTSE:SHOP, XCNQ:...), newest first: annual and interim financial statements, MD&A, annual information forms, information circulars, news releases, material change reports and prospectuses. Each row gives the filing date, the regulator's category, the document name and a link that opens the document (a PDF) on its Equibles page. Narrow with query, whose words must all appear in the document name or category (e.g. 'financial statements', 'MD&A', 'circular'), and with a date range. The documents' text is not searchable: ListFilings, SearchDocuments and ReadDocumentLines cover SEC filings and transcripts, which a Canadian company has only when it also files with the SEC. For reported figures use GetFinancialStatement.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "GetCanadianFilings"
  }
}

Input Schema

Name	Required	Description
`query`	No	Optional words (at most 6) that must all appear in the document name or category, in any case, e.g. 'annual financial statements', 'MD&A', 'information circular'.
`offset`	No	Rows to skip for paging (default 0).
`ticker`	Yes	Canadian listing symbol MIC:TICKER, e.g. XTSE:SHOP. A bare ticker names a US listing and is answered with the company's Canadian listings to ask with.
`endDate`	No	Optional latest filing date, YYYY-MM-DD.
`startDate`	No	Optional earliest filing date, YYYY-MM-DD.
`maxResults`	No	Maximum filings, newest first (default 20, max 100).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description goes well beyond that by disclosing result ordering (newest first), the exact shape of each row (filing date, regulator category, document name, PDF link on Equibles), and the crucial behavioral constraint that full text is not searchable. Those are the details an agent needs to interpret results and avoid dead-end queries.

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?

Purpose, scope and document types are front-loaded, then filtering, then sibling routing — a sensible order. It is a single dense paragraph with long clauses, and the query example list overlaps the schema examples, but no sentence is purely filler.

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?

For a six-parameter read-only listing tool with no output schema, the description supplies the return-row structure, ordering, and the limits of filtering, which is everything needed to call it and interpret the response. Nothing material is left for the agent to guess.

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 ticker format (MIC:TICKER), query word limits, date formats and maxResults are all already documented. The description restates the query filter ('words must all appear in the document name or category') and offers example values, but adds little beyond the schema, and it does not mention paging via offset. 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 and resource — 'List the documents a company listed in Canada filed on SEDAR+' — and enumerates the document types covered (financial statements, MD&A, AIFs, circulars, news releases, material change reports, prospectuses). It also pins the scope to a single Canadian listing and explicitly separates itself from the SEC-oriented siblings, so an agent can tell it apart 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit exclusions: the documents' text is not searchable, and ListFilings, SearchDocuments and ReadDocumentLines cover SEC filings and transcripts, which Canadian issuers only have if they also file with the SEC. It also routes agents wanting figures to GetFinancialStatement, so the 'use this instead' path is unambiguous.

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

All Equibles tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.