Equibles

Canadian Short Positions (CIRO)

GetCanadianShortPositions

Read-only

Get the aggregate short positions in one Canadian listing, written MIC:TICKER (e.g. XTSE:RY, XTSX:..., XCNQ:..., NEOE:...), from CIRO's Consolidated Short Position Report, newest first. CIRO, the Canadian Investment Regulatory Organization, publishes one report as of the 15th and one as of the last day of each month, a few days later. Each row gives the as-of date, the short position in shares, CIRO's net change since its previous report, and the listing's average daily volume over the trading days since the previous as-of date with the days to cover it implies, both from our own daily volume for that listing, and the shares CIRO reports sold short over the period with their percentage of all shares traded, with CIRO's later corrections applied. Capture began with the reports CIRO still served at its first read, about a year back. For US short interest use GetShortInterest; for European short positions use GetEuropeanShortPositions.

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

Input Schema

Name	Required	Description
`offset`	No	Rows to skip for paging (default 0).
`ticker`	Yes	Canadian listing symbol MIC:TICKER, e.g. XTSE:RY. A bare ticker names a US listing and is answered with the company's Canadian listings to ask with.
`maxResults`	No	Maximum reports, newest first (default 24, about a year; max 100).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, non-destructive and closed-world, so the safety bar is low. The description goes well beyond that with source provenance (CIRO Consolidated Short Position Report), publication cadence (as of the 15th and month-end, published a few days later), history depth (~one year), and that CIRO corrections are applied. It does not mention pagination limits beyond maxResults or error behavior, keeping it short of a 5.

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 and identifier format are front-loaded, and the trailing sibling routing is well placed. The middle sentence describing row contents is a dense run-on that could be split, but every clause carries information an agent would otherwise have to guess.

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 must describe return values, and it does: as-of date, short position in shares, CIRO net change, average daily volume and days to cover from the provider's own volume, and short volume with percentage of shares traded. Coverage window and correction handling close the remaining gaps for this read-only tool.

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 100%, so baseline is 3, but the description adds real meaning: the MIC prefix vocabulary (XTSE, XTSX, XCNQ, NEOE) beyond the schema's single example, and the bare-ticker fallback behavior. It reinforces that results are newest first, matching maxResults' semantics.

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 ('aggregate short positions in one Canadian listing') and pins down the exact identifier format MIC:TICKER with enumerated MIC examples. It explicitly distinguishes itself from GetShortInterest and GetEuropeanShortPositions, so an agent can route correctly without opening a 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 alternatives and the condition selecting each: US short interest goes to GetShortInterest, European positions to GetEuropeanShortPositions. It also handles the mis-invocation case, explaining that a bare ticker names a US listing and returns the Canadian listings to ask with.

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.