Skip to main content
Glama

company

Identify a Korean listed company by name, ticker, or corp_code, and retrieve its market, industry, and recent public filings.

Instructions

desc: 기업 식별 + 최근 공시 인덱스. 모든 data tool 공통 입구. 회사명/ticker/corp_code → 시장·업종·최근 공시. when: 검색 시작 → ticker/corp_code 확정 후속 tool에 전달. 최근 공시 종류·빈도 훑을 때. rule: 비상장 법인 자동 제외 (상장사 전용). 공식 한글·영문명과 별칭을 우선하고, 부분명은 활성 상장·시총 격차가 충분할 때만 자동 추론. 공식명 exact는 시총보다 우선. params: query, max_recent_filings(1-20), start_date/end_date(YYYYMMDD), language(auto|ko|en) ref: shareholder_meeting_notice, ownership_structure, dividend, proxy_contest, value_up

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
formatNomd
end_dateNo
languageNoauto
start_dateNo
max_recent_filingsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations present, so description carries full burden. Discloses automatic exclusion of unlisted companies, name matching logic, and parameter constraints. Lacks rate limit or auth details but still good.

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?

Very concise with purpose, usage, rules, and parameters all in a few lines. No wasted words.

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 (6 parameters, many siblings) and presence of output schema, the description provides sufficient guidance for an AI agent to use it effectively.

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 0%, but description adds context for max_recent_filings (range 1-20), date format YYYYMMDD, and language options. However, it omits the 'format' parameter and doesn't explain the 'query' parameter's expected input.

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?

Clearly states the tool identifies companies and provides recent filing index, and it's the common entry point for all data tools. Distinguishes from siblings by being the entry tool.

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?

Explicitly tells when to use (start of search, to get identifiers for subsequent tools, to browse recent filings) and provides a rule about excluding unlisted companies and name matching priority.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MarcoYou/open-proxy-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server