Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Canada Feed (SEDAR+ material changes + Canadian issuers' US 424s)

canada_feed
Read-onlyIdempotent

Kaleidoscope Console's Canada Feed: one timeline of Canadian issuers' SEDAR+ material change reports (every vouched report, typed and summarised by MARS) and their US 424 prospectuses (EDGAR; bank structured notes left out). Newest first. Each row: date, kind (mc material change / p424), event type and label, company (name, ticker, CIK, market cap), MARS id, SEDAR+ profile, province, sector, one-paragraph summary, accession (material changes: pass to sedar_document).

Filters: window days 7 / 30 / 90 / 180 / 365 (default 30); type: financing_offering Financing; acquisition_divestiture Acquisition / divestiture; merger_takeover Merger / takeover; management_change Management change; board_change Board change; operational_project Operations / project; legal_regulatory Legal / regulatory; earnings_guidance Earnings / guidance; dividend_distribution Dividend; other Other; p424 US prospectus (424); province (e.g. 'British Columbia', 'Canada, province not known', 'Outside Canada', 'Not known'); sector (GICS-like: 'Materials', 'Energy', 'Financials'... or 'Unclassified'); cap '100m' / '1b' / '10b' (minimum market cap; issuers with no cap drop out); q (issuer name substring, exact ticker or CIK); notes (show 424B2 note supplements — RY / TD file several a day); tickers / ciks (only these issuers; replaces Console's watchlist toggle).

Also returns Console's KPIs (events, issuers, financings, M&A, management & board, US 424s, equity raised in 424s) and facets (type / province / sector counts, each computed with the other filters on). Console shows the newest 1,500 rows; limit (default 25) / offset page through them.

Province: atlas EDGAR address when it says Canada, else MARS's record folded (names, postal codes, EDGAR codes), else GLEIF jurisdiction. Sector: MARS sector / industries by keyword, else SIC. Market cap: US listing's cap, else TSX / TSXV cap. Big issuers rarely file material change reports (TD 10 ever): for them the feed is mostly 424s.

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

Input Schema

NameRequiredDescriptionDefault
qNo
capNo
ciksNoOnly these CIKs (max 200).
typeNo
as_ofNoYYYY-MM-DD: the window ends on this date instead of today.
limitNoRows to return (0-1500).
notesNoInclude 424B2 note pricing supplements.
offsetNo
sectorNo
windowNo
tickersNoOnly these issuers (ticker, SEDAR:<no.>, TSX:/TSXV:<symbol>, MARS id; max 50).
provinceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), and the description adds substantial behavior beyond them: a 1,500-row Console cap with limit/offset paging, computed KPIs and facets (each facet computed with the other filters applied), explicit exclusion of bank structured notes, the `notes` toggle for 424B2 pricing supplements, and the caveat that issuers with no market cap drop out when `cap` is used. It even warns about the base-rate skew — big issuers like TD rarely file material change reports, so for them the feed is mostly 424s — which materially shapes how an agent should interpret results.

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?

Front-loaded with the purpose and row shape, then organized into a filter catalogue and a methodology block, with bolding to aid scanning. Some of the `type` value list restates the schema enum nearly verbatim (only the human-readable labels are new), and the province/sector/cap derivation sentences are dense. Efficient overall for the amount of information conveyed, but not maximal concision.

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 12-parameter, all-optional feed with no output schema, the description supplies what is otherwise missing: row fields, the KPI and facet returns, the 1,500-row display cap and paging, and the derivation rules that determine filter values. The caveat about large issuers generating mostly 424s closes the main interpretive gap an agent would hit when results look sparse.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 42%, so the description must carry the load and it does: it explains every filter's meaning and edge cases, including that `cap` drops uncapped issuers, that `q` matches name substring or exact ticker/CIK, that `notes` adds 424B2 supplements, that `province` accepts values like 'Outside Canada' and 'Not known', and that `tickers`/`ciks` supersede the watchlist. It also documents the derivation logic for province, sector and market cap, which the schema says nothing about.

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?

Opens with a specific verb+resource: a single timeline of Canadian issuers' SEDAR+ material change reports plus their US 424 prospectuses, newest first. It enumerates exactly what each row contains (date, kind, event type, company, MARS id, province, sector, summary, accession), so an agent knows the output shape before calling. It also distinguishes itself from the filing-level siblings by scoping to material changes and 424s and by routing to `sedar_document` for the underlying document.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is heavily implied by the filter catalogue (window, type, province, sector, cap, tickers/ciks) and by the note that `tickers`/`ciks` replaces Console's watchlist toggle, plus the follow-up routing 'material changes: pass to `sedar_document`'. However, it never states when to reach for this feed instead of `sedar_filings` or `sedar_search`, and gives no exclusions beyond excluding bank structured notes. Adequate but leaves alternative selection to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources