Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Canadian SEDAR+ Filing Search (semantic or keyword, 2026 on, with doc text)

sedar_search
Read-onlyIdempotent

Search Canadian SEDAR+ filings (TSX / TSXV / CSE issuers and funds): news releases, prospectuses, financial statements, MD&A, material change reports, proxy circulars, technical reports and more, one result per filed document. Coverage: filings from 2026-01-01 on, updated as sections loads them.

mode='semantic' (default) ranks by meaning (learned-sparse, like semantic_search); mode='keyword' ranks by exact words. Either way the snippet shows matching text. Filters: ticker, company (filer name), issuer_no, filing_type (e.g. news_releases, material_change_report, annual_mda, interim_mda, annual_financial_statements, management_proxy_materials, shelf_prospectus_ni_44102), date_from / date_to. With filters and no query, the newest filings come first.

Each result cites its source: doc_id (one PDF), accession (the SEDAR+ document id) and package_id (the filing package). Pass doc_id to get that document's text (up to 20,000 characters, max_chars). Scanned PDFs have no text (text_quality='scanned_no_text').

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": "sedar_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNosemantic
limitNoResults (max 50).
queryNoWhat to look for, e.g. 'updated lithium mineral resource estimate'.
doc_idNoReturn this one document with its text instead of searching.
tickerNoCanadian ticker without exchange, e.g. 'LAR' (comma-separated for several).
companyNoFiler name, matched loosely, e.g. 'Lithium Argentina'.
date_toNoYYYY-MM-DD, filing date on or before.
date_fromNoYYYY-MM-DD, filing date on or after.
issuer_noNoSEDAR+ issuer number, e.g. '000027103'.
max_charsNoText length for doc_id (max 20,000).
filing_typeNoOne or more filing types (comma-separated or list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses coverage boundaries (2026-01-01 onward), freshness ('updated as sections loads them'), the citation structure returned per hit (doc_id, accession, package_id), the 20,000-character text cap with max_chars, and the meaningful failure mode that scanned PDFs yield no text (text_quality='scanned_no_text'). These are exactly the constraints an agent needs before committing to a query strategy.

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?

Three tight paragraphs: what it searches, how modes and filters behave, then what each result carries. Front-loaded with the highest-value facts and no filler. Slightly dense — the long filing_type enumeration sits inline rather than in a list, which mildly hurts scanability.

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?

Eleven optional parameters and no output schema, so the description must carry the return-shape burden — and it does, naming doc_id, accession, package_id, and the snippet. Combined with the coverage window and scanned-PDF caveat, an agent has everything needed to call it correctly on the first attempt.

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

Parameters4/5

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

Schema coverage is already 91%, so the baseline is 3, and the description earns extra credit by supplying concrete filing_type values (news_releases, annual_mda, shelf_prospectus_ni_44102, etc.) that the schema documents only abstractly, plus the behavioral rule that filters with no query sort by newest filing. It adds little on ticker/company/issuer_no formatting beyond what the schema already states.

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?

The description opens with a specific verb+resource ('Search Canadian SEDAR+ filings'), enumerates the document classes covered (news releases, prospectuses, financial statements, MD&A, material change reports, proxies, technical reports), and states the result granularity ('one result per filed document'). It also distinguishes its two internal modes ('semantic' ranks by meaning, 'keyword' by exact words) and its doc_id retrieval path, so an agent can tell it apart from a generic semantic_search.

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?

Clear operational guidance: which mode is default, how each ranks, what happens 'with filters and no query' (newest first), and that doc_id should be passed to fetch a document's text. The gap is sibling routing — semantic_search is invoked only as an analogy for ranking behavior, and no condition is given for choosing this tool over get_filing or semantic_search when both could serve.

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