Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

SEDAR+ Document Text (one filing by accession)

sedar_document
Read-onlyIdempotent

The text of one SEDAR+ filing by its accession — the document Kaleidoscope Console opens from 'SEDAR+ Filings', the Canada Feed and Mining Projects (Console shows the PDF; this returns the text extracted from it). Accessions come from sedar_filings, canada_feed (material change reports) and mining_projects (technical reports), e.g. '06510971-00000001-000016960-20261107-PDF'. Only SEDAR+ accessions on record in MARS are served (SEC accessions: use get_filing).

Returns filer, filing date, SEDAR+ type, the PDF's availability and the text (max_chars, default 20,000; offset to read on; total_chars says how long it is). Long technical reports run to hundreds of thousands of characters: read in pieces or search with sedar_search first.

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": {
      "accession": "<accession>"
    },
    "name": "sedar_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNoCharacter offset to start from.
accessionYesSEDAR+ accession (MARS's), as returned by the other sedar tools.
max_charsNo1-200000

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond read-only and idempotent annotations, the description explains what is returned, that the text is extracted from the PDF, that only MARS-recorded SEDAR+ accessions are served, and how pagination behaves for long documents. This provides meaningful operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and uses compact sentences to add distinctions, sources, return fields, and pagination guidance. There is no unnecessary repetition or filler.

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 adequately explains the returned fields, PDF availability, text pagination via max_chars and offset, and total length via total_chars. It is complete enough for correct invocation.

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 the schema already documents offset max_chars, and accession. The description adds useful meaning through a concrete accession example and guidance that long filings should be read in pieces using max_chars and offset.

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: returning the text of one SEDAR+ filing by accession. It distinguishes this from sibling tools by naming sedar_filings, canada_feed, mining_projects as accession sources and get_filing for SEC accessions.

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 clear conditions: use this for SEDAR+ accessions on record in MARS, use get_filing for SEC accessions, and read long technical reports in pieces or search with sedar_search first. The alternatives and workflow guidance are explicit.

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