Skip to main content
Glama
daniel3303

Equibles

by daniel3303
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Search SEC Filings

SearchDocuments
Read-only

Search SEC filings and earnings-call transcripts by keyword, semantic meaning, or exact phrase. Filter by ticker, date, or document type and get excerpts with document IDs.

Instructions

Search SEC filings and earnings-call transcripts with hybrid keyword and semantic retrieval, or with match 'phrase' for only the excerpts containing an exact phrase. Omit ticker to search every company, or provide one ticker to search only that company. Returns excerpts with document IDs for SearchDocument or ReadDocumentLines. Use excludeTickers and maxResultsPerCompany only for market-wide discovery; use ListFilings to browse filings newest first without a text query.

Input Schema

NameRequiredDescriptionDefault
matchNoHow the query matches: 'ranked' (default — relevance-ranked keyword and semantic retrieval that broadens to any of the words when results are sparse) or 'phrase' (only excerpts containing the query's words consecutively and in order; case and punctuation are ignored).ranked
queryYesSearch query — plain keywords or a short natural-language phrase. In ranked mode, when too few excerpts match every word, the search automatically broadens to match any of the words; concise, filing-phrased terms (e.g. 'Data Center revenue') still rank best. In phrase mode, the exact phrase to find.
tickerNoOptional company ticker; a listing outside the US is MIC:TICKER (e.g. XPAR:AIR). Omit to search across all companies.
endDateNoOptional end date filter in YYYY-MM-DD format
startDateNoOptional start date filter in YYYY-MM-DD format
maxResultsNoMaximum number of results to return (default: 5, max: 500)
documentTypesNoOptional document types. Accepts registered values such as TenK, TenQ, EightK, TwentyF, SixK, FortyF, Def14A, SOne, or deployment-registered types such as EarningsCallTranscript. SEC form names such as 10-K, DEFA14A, S-3, SC TO-T or NT 10-K are also accepted; an invalid value returns the full accepted list.
excludeTickersNoOptional tickers to exclude from a market-wide search (max 25). Cannot be combined with ticker.
maxExcerptCharsNoMaximum characters per excerpt (default: 0 = full excerpt). Set a small value (e.g. 400) for a compact scan across many results; truncated excerpts end with an explicit note.
maxResultsPerCompanyNoMaximum results from any single company (default: 0 = unlimited). Set a small value (e.g. 2) to spread results across more companies for discovery-style queries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

The readOnlyHint annotation already covers safety, and the description adds substantial behavioral context: hybrid keyword/semantic retrieval, ranked-mode broadening, exact phrase behavior, excerpt return format, and document IDs for follow-up tools. It is consistent with the read-only annotation.

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 and compact for a 10-parameter tool. Each sentence conveys useful selection or behavior information without repetition.

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?

The description covers the key search behavior, scope controls, and return excerpts with document IDs. Because there is no output schema, a fuller description of the returned excerpt object would be ideal, but the essential information for calling the tool is present.

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 most parameter meaning is already documented. The description adds cross-parameter usage guidance, especially for ticker scope and for excludeTickers/maxResultsPerCompany in market-wide discovery, but it does not add detail for every parameter.

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: searching SEC filings and earnings-call transcripts. It distinguishes retrieval modes and names related tools such as SearchDocument, ReadDocumentLines, and ListFilings.

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 explicit selection guidance: omit ticker to search all companies, provide one ticker to narrow, use phrase mode for exact excerpts, and use ListFilings instead when browsing without a text query. It also explains when excludeTickers and maxResultsPerCompany are appropriate.

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

Deploy Server

Other Tools