Skip to main content
Glama
Johnhyeon

StockLens

by Johnhyeon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_us_filing_detail

Read-onlyIdempotent

Search US SEC filing text by ticker and accession number for keywords, and extract structured dilution or contract clauses with original excerpts.

Instructions

US SEC filing 본문 — 원문 키워드 검색·희석/계약 조항 구조화 (SL-04).

  • find: 본문에서 키워드 주변 발췌(전체 매치 수 + 최대 5건 표시). 매치 0건은 "본문에 없다"가 아니다 - 표기가 다를 수 있다.

  • analyze: "dilution"(증권 수·전환가·워런트·리픽싱·자금용도) 또는 "contract"(계약금액·기간·해지·최소구매·상대방 비공개)를 범주별 원문 발췌로 구조화. 못 찾은 범주는 '미확인'이지 '없다'가 아니다.

  • 둘 다 비우면 문서 목록(본문+exhibit)만 보여준다. 전체 본문은 반환하지 않는다(10-Q 하나가 수십만 자다).

Args: ticker: US 티커 (발행사 CIK 확인용) accession_no: SEC 접수번호 (get_us_filings 결과의 accession) find: 본문 검색 키워드 (선택) analyze: "dilution" / "contract" (선택) document: 읽을 문서 파일명 (비우면 본문. exhibit 는 목록에서 이름 확인)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
findNo
tickerYes
analyzeNo
documentNo
accession_noYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.1.3
    • removedInput schema / properties / analyze / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / analyze / default
      Removed value: -null
    • addedInput schema / properties / analyze / type
      Added value: +"string"
    • removedInput schema / properties / document / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / document / default
      Removed value: -null
    • addedInput schema / properties / document / type
      Added value: +"string"
    • removedInput schema / properties / find / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / find / default
      Removed value: -null
    • addedInput schema / properties / find / type
      Added value: +"string"
  2. Addedv1.0.1

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description adds valuable caveats: a zero-match result does not mean the term is absent, unfound categories are 'unconfirmed' rather than 'absent', and both-empty mode returns only a document list. These disclosures materially shape an agent's interpretation of results.

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 bulleted structure is efficient and front-loaded, with each behavior and parameter earning its place. The 'SL-04' label adds little value but does not significantly hurt clarity.

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?

Given the tool's complexity and 5 parameters, the description covers all necessary guidance: parameter semantics, mode behavior, output limits, omission semantics, and document handling. An output schema exists, so not detailing return fields is acceptable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by explaining each parameter's purpose: ticker for CIK lookup, accession_no as the SEC receipt number from get_us_filings, find as a keyword, analyze as the dilution/contract mode, and document as the file to read, including default behavior.

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 clearly states the tool's purpose: searching keywords in US SEC filing text and structuring dilution/contract clauses by category. It also specifies what the tool does not do (does not return the full text) and distinguishes itself from the filing-list sibling by requiring an accession_no from get_us_filings.

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

Usage Guidelines4/5

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

The description gives clear usage context: use find for keyword excerpts, analyze for dilution/contract structuring, leave both empty for a document list, and use document to read a specific file. It also includes an explicit exclusion ('does not return full text'), though it does not name alternative sibling tools directly.

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