Skip to main content
Glama

Canadian Insider Transactions (SEDI)

GetCanadianInsiderTransactions
Read-only

Get the insider transactions filed on SEDI, Canada's insider disclosure system, for the issuer of one Canadian listing, written MIC:TICKER (e.g. XTSE:ATD, XTSX:..., XCNQ:..., NEOE:...), newest first. Each row gives the transaction date, the insider and their relationship to the issuer, the registered holder for indirect holdings, the SEDI transaction type, the security (options, share units and warrants included, with the underlying where filed), the signed amount (negative for a disposition) in units of that security, the price and its currency, the holding after the transaction and the filing date. An amended transaction appears once, at its newest amendment. Capture began with about the year before it first ran and grows daily, so older history is missing. For US Form 4 filings use GetInsiderTransactions; for European director dealings use GetEuropeanDirectorTransactions.

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

Input Schema

NameRequiredDescriptionDefault
offsetNoRows to skip for paging (default 0).
tickerYesCanadian listing symbol MIC:TICKER, e.g. XTSE:ATD. A bare ticker names a US listing and is answered with the company's Canadian listings to ask with.
maxResultsNoMaximum transactions, newest first (default 20, max 100).

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 annotations, the description discloses important behavior: results are newest first, amended transactions appear once at their newest amendment, and historical coverage starts about a year before first capture and grows daily. These are exactly the traits an agent needs to interpret completeness and duplicate handling.

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?

The purpose and identifier format are front-loaded, and every sentence contributes useful information. The long single-paragraph enumeration of row fields is dense but justified because there is no output schema; minor formatting would improve readability.

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 fully explains the returned row fields, ordering, amendment handling, coverage limitations, and sibling alternatives. Nothing material is missing for an agent to call and interpret this tool correctly.

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 the schema already documents ticker, offset, and maxResults. The description reinforces the MIC:TICKER format and provides additional exchange examples, but adds no paging or result-limit semantics beyond the schema, making the baseline 3 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?

The description states a specific verb and resource (insider transactions filed on SEDI) for a precisely scoped issuer listing, and explicitly distinguishes this Canadian tool from the US and European sibling tools. An agent can identify the tool and its domain without opening the 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?

It gives an explicit identifier format (MIC:TICKER) and names the alternatives with their conditions: GetInsiderTransactions for US Form 4 and GetEuropeanDirectorTransactions for European director dealings. This directly routes the agent between siblings.

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.