Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Mining Projects (NI 43-101: stage, NPV / IRR, P&P / M&I, screen or company)

mining_projects
Read-onlyIdempotent

NI 43-101 mining projects from SEDAR+ technical reports — Kaleidoscope Console's 'Mining Projects' (app and company report). One project per company at its latest technical report; earlier reports listed under it. Each project: name, company (name, ticker, CIK, MARS id), stage (production / feasibility / PFS / PEA / exploration / unknown), commodities, country / region, study economics (NPV US$M with its basis, IRR %, capex US$M, mine life, discount rate, tax basis, price deck), headline reserves (P&P), resources (M&I) and inferred lines (contained metal + tonnes), report date and accession (sedar_document reads it).

With an issuer (issuer / cik / profile_number / mars_company_id): the company report — every project with the latest report's full headline reserve / resource table (category, zone, cutoff, tonnes Mt, grades, contained, effective date), production first then by NPV. Works for issuers with no CIK.

Without an issuer: the screen. Filters commodity (a name: 'Gold', 'Copper', 'Lithium', 'Uranium', 'Rare earths'...), stage, country ('Canada', 'United States', 'Not stated'...), econ (NPV stated), npv_min (US$M), irr_min (%), q (project / company substring, exact ticker or CIK). KPIs: projects, companies, with economics, total NPV, median IRR, in production; facets for commodity / stage / country. Rows newest report first (Console's order) or sort by npv / irr; Console shows 1,500; limit (default 25) / offset.

Rules: reserves = P&P (else probable / proven), resources = M&I (else indicated / measured), the combined line first then most tonnes, zero-tonnage lines dropped; project name variants folded ('Almas' = 'Almas Project'); commodity symbols mapped (sb -> Antimony, U3O8 -> Uranium), grade-only elements and metal equivalents dropped. Economics on ~1 project in 5; effective dates sparse. For the 7 US-listed gold majors' company-level reserves / production / AISC (SK-1300) see mining_company_reserves.

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

Input Schema

NameRequiredDescriptionDefault
qNo
cikNoSEC CIK (alternative to `issuer`).
econNoOnly projects with a stated NPV.
sortNodate
as_ofNoYYYY-MM-DD: only technical reports filed on or before this date.
limitNoScreen rows to return (0-1500).
stageNo
issuerNoThe issuer: a US ticker or CIK (cross-listed issuers, e.g. 'TD' or '947263'); 'SEDAR:<issuer number>' (the SEDAR+ profile, e.g. 'SEDAR:1369' or 'SEDAR:000001369'); 'TSX:<symbol>' / 'TSXV:<symbol>' for a Canadian listing (e.g. 'TSXV:RSM'); a MARS company id (uuid, for issuers with no CIK); or a company name. A plain ticker is read as a US ticker first (as Console's Excel add-in does): 'OGN' is Organon, 'TSXV:OGN' is Orogen Royalties.
offsetNo
countryNo
irr_minNoMinimum IRR, %.
npv_minNoMinimum NPV, US$M.
commodityNo
include_tableNoCompany mode: include each project's full reserve / resource table.
profile_numberNoSEDAR+ issuer / profile number (alternative to `issuer`).
mars_company_idNoMARS company id (uuid) — for SEDAR+ issuers with no CIK.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare read-only, idempotent, non-destructive, closed-world, so the description carries the substantive disclosure: one project per company at its latest report with earlier reports nested, reserve/resource line-selection rules (P&P else probable/proven; M&I else indicated/measured; combined line first), zero-tonnage lines dropped, name-variant folding, commodity-symbol mapping, and dropped grade-only/equivalents. It also warns that economics exist on only ~1 in 5 projects and effective dates are sparse, and that the Console screen caps at 1,500 rows with a default limit of 25. What keeps it from a 5 is the absence of any note on error behavior for malformed issuer identifiers or what happens when a screen returns zero rows.

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 description is long but deliberately structured — bold headers separate the data model, the with-issuer mode, the screen mode, and the transformation rules, and the two modes are front-loaded right after the source statement. Almost every clause carries operational content rather than restating the title. It is dense enough that a reader must slow down, which costs it the top mark.

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 16-parameter tool with no output schema, the description documents the returned shape in detail: per-project fields (name, company identifiers, stage, commodities, geography, NPV basis, IRR, capex, mine life, discount rate, tax basis, price deck, P&P/M&I/inferred lines, report date, accession), the company-mode table columns, and the screen's KPIs and facets. Combined with the data-quality caveats, an agent has enough to call it correctly and interpret what comes back.

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 63%, and the description fills the largest gaps: it gives accepted commodity names, country values including 'Not stated', the meaning of econ (NPV stated) and npv_min/irr_min units, and defines q as a project/company substring or exact ticker/CIK (the schema leaves q undocumented). It adds the ticker-precedence nuance (a plain ticker resolves as US first, so 'TSXV:OGN' differs from 'OGN') and confirms include_table's company-mode role. Minor slack remains: 'limit' / 'offset' interaction and 'as_of' filtering are only lightly touched beyond the schema.

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 opening line names the specific source (SEDAR+ NI 43-101 technical reports) and resource, and immediately splits the tool into its two modes: company report with an issuer, screen without one. It explicitly names the sibling it is not (mining_company_reserves for US-listed gold majors' SK-1300 company-level figures), so an agent can tell the two apart without opening either 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?

States the selection condition for each mode explicitly: supplying issuer/cik/profile_number/mars_company_id yields the company report, omitting them yields the screen, and the screen's filters are enumerated with example values. It also routes a specific adjacent need (US-listed gold majors SK-1300 reserves/production/AISC) to mining_company_reserves, and notes the company report works for issuers with no CIK.

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