Skip to main content
Glama

Server Details

SEC fundamentals point in time: first reported, known as of a date, every restatement.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
arhancanli/canlicapital
GitHub Stars
0

TDQS

A3.5/5.0

Scored across 7 tools

Disambiguation4/5

Each tool has a distinct output shape and use case: find_company for identity, list_concepts for available metrics, history for time series, known_as_of for point-in-time snapshots, cross_section for peer comparisons, restatements for changed values, and vintages for revision history. Some conceptual overlap remains around point-in-time/restatement queries, but the descriptions clearly differentiate them.

Naming Consistency3/5

All names use snake_case, but the conventions are mixed: find_company and list_concepts are verb_noun, while cross_section, history, known_as_of, restatements, and vintages are nouns or adjective phrases. The names are still readable and not chaotic.

Tool Count5/5

Seven tools is well-scoped for a specialized SEC/XBRL fundamentals service, with each tool covering a distinct analytical need. There is no obvious redundancy or missing basic operation that would require additional tools.

Completeness4/5

The surface covers discovery, concept metadata, time-series history, point-in-time snapshots, cross-sectional peer analysis, restatement detection, and vintage revision history. Minor gaps exist, such as assembling a full financial statement in one call, but the core point-in-time fundamentals workflow is covered.

Available Tools

7 tools
cross_sectionCross-section as of a date
Read-onlyIdempotent
Inspect

Get one measure for up to 50 companies as filed by a date: each one's latest period, its value then, and whether it was later restated. For point-in-time peer and factor work.

ParametersJSON Schema
NameRequiredDescriptionDefault
as_ofYesOnly filings on or before it count.
conceptYesPlain name (revenue, eps_diluted, assets; follows tag changes) or XBRL tag (Revenues).
periodsNoannual (default) or quarterly.
companiesYesTickers, CIKs or names.

Output Schema

ParametersJSON Schema
NameRequiredDescription
rowsNo
as_ofNo
limitsNo
columnsNo
conceptNo
meaningNo
missingNo
companiesNo
truncatedNo
next_offsetNo
find_companyFind a companyB
Read-onlyIdempotent
Inspect

Find a company's SEC CIK and tickers by name, ticker or CIK. The other tools also take a name as company.

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoDefault 8.
queryYesName (Exxon Mobil), ticker or CIK.

Output Schema

ParametersJSON Schema
NameRequiredDescription
rowsNo
queryNo
totalNo
limitsNo
columnsNo
meaningNo
resolvedNo
truncatedNo
next_offsetNo
ticker_holderNo

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds nothing beyond that – no note on open-world lookups, result ambiguity, or match behavior. It does not contradict annotations, so no flag.

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?

Two very short sentences, front-loaded with the core purpose. The trailing sibling remark is of limited value but costs little space; sizing is appropriate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. The description covers the core lookup and inputs adequately; only guidance on result handling/open-world behavior is missing.

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%: both query and limit are documented in the schema. The description's mention of 'name, ticker or CIK' duplicates the schema's query description without adding format or semantics. Baseline 3 for fully documented parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a clear verb+resource ('Find a company's SEC CIK and tickers') and specifies the accepted input identifiers (name, ticker, CIK). It does not differentiate from siblings like cross_section or history, but those appear to be unrelated data-retrieval tools rather than overlapping lookups.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence 'The other tools also take a name as company' is an observation about sibling tools, not guidance on when to use this tool. No when-to-use, when-not, or alternative-selection guidance is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

historyMeasure history
Read-onlyIdempotent
Inspect

Get one measure over time, newest first: as first reported (default), as latest filed, or as known on as_of, each with its filing and whether it later changed.

ParametersJSON Schema
NameRequiredDescriptionDefault
unitNoDefault: the unit with most periods.
as_ofNoOnly filings made on or before this date count, for every basis.
basisNofirst_reported (default), latest, or as_of (default when as_of is set).
limitNoDefault 20, newest first.
companyYesTicker (AAPL), CIK or company name.
conceptYesPlain name (revenue, eps_diluted, assets; follows tag changes) or XBRL tag (Revenues).
periodsNoannual (default), quarterly, or all (adds year-to-date).

Output Schema

ParametersJSON Schema
NameRequiredDescription
rowsNo
basisNo
totalNo
limitsNo
columnsNo
companyNo
conceptNo
meaningNo
snapshotNo
truncatedNo
next_offsetNo
known_as_ofKnown as of a date
Read-onlyIdempotent
Inspect

Get what a company had reported as of a date: per measure, the latest period filed by then, its value, and whether it was later restated; optionally ratios from those filings. For point-in-time backtests.

ParametersJSON Schema
NameRequiredDescriptionDefault
as_ofYesDecision date: only filings on or before it count.
ratiosNoAdds margins, ROE, ROA, leverage, free cash flow.
companyYesTicker (AAPL), CIK or company name.
periodsNoannual (default) or quarterly.
conceptsNoDefault: ten common measures.

Output Schema

ParametersJSON Schema
NameRequiredDescription
rowsNo
as_ofNo
limitsNo
ratiosNo
columnsNo
companyNo
meaningNo
missingNo
snapshotNo
truncatedNo
next_offsetNo
list_conceptsList concepts
Read-onlyIdempotent
Inspect

List the XBRL concepts a company reports and the plain names it supports, with units, periods, date range and restated-period counts.

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoDefault 40.
offsetNonext_offset from the last page.
searchNoWords in concept names or labels, e.g. revenue.
companyYesTicker (AAPL), CIK or company name.

Output Schema

ParametersJSON Schema
NameRequiredDescription
rowsNo
limitsNo
columnsNo
companyNo
matchedNo
meaningNo
conceptsNo
snapshotNo
truncatedNo
next_offsetNo
plain_namesNo
restatementsRestated periods
Read-onlyIdempotent
Inspect

List periods whose value changed in a later filing, with first and latest values, % change and cause (stock splits left out by default). Omit concept to scan everything.

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoDefault 25, newest first.
sinceNoOnly periods ending on or after.
offsetNonext_offset from the last page.
companyYesTicker (AAPL), CIK or company name.
conceptNoDefault: every concept.
periodsNoannual (default), quarterly, or all (adds year-to-date).
include_splitsNoAlso list stock-split changes; default false.
min_change_pctNoMinimum absolute change, % of first value.

Output Schema

ParametersJSON Schema
NameRequiredDescription
rowsNo
limitsNo
changedNo
columnsNo
companyNo
meaningNo
scannedNo
snapshotNo
truncatedNo
next_offsetNo
vintagesFiling vintages
Read-onlyIdempotent
Inspect

List every filing that reported one period of one measure, oldest first: the revision history behind a number.

ParametersJSON Schema
NameRequiredDescriptionDefault
endYesPeriod end.
unitNoDefault: the unit with most periods.
startNoPeriod start, when several periods share the end (quarter vs year-to-date).
companyYesTicker (AAPL), CIK or company name.
conceptYesPlain name (revenue, eps_diluted, assets; follows tag changes) or XBRL tag (Revenues).

Output Schema

ParametersJSON Schema
NameRequiredDescription
rowsNo
limitsNo
columnsNo
companyNo
conceptNo
meaningNo
snapshotNo
truncatedNo
filing_urlNo
next_offsetNo

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 7 tool updates
    • First observedcross_section
    • First observedfind_company
    • First observedhistory
    • First observedknown_as_of
    • First observedlist_concepts
    • First observedrestatements
    • First observedvintages

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI assistants to look up SEC company fundamentals point in time: what a company first reported, what was known on any given date, and which values were later restated, with the filing behind each value. Supports querying history over time, tracing every vintage of a period, and resolving measures such as revenue or EPS across the XBRL tags a company has used.
    124 npm
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    Provides as-reported US equity fundamentals, live quotes, financial statements, valuation comps, and a screener from SEC filings, with per-cell filing provenance for citations.
    7
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Provides free SEC filing fundamentals for US public companies, including financial statements, 10-K/10-Q summaries, and 8-K event histories. No API key or signup required.
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    SEC-filed financial statements back to 1985 for US-listed companies, plus global coverage, every number cited to its filing with an accession number. 59 tools for income statements, balance sheets, cash flow, growth rates, valuation (DCF, reverse DCF, comparables, fair-value range), SEC filing and earnings-call search, supply chains, 13F holders, options positioning and thesis monitoring.
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.