Skip to main content
Glama
meteoroh

tossinvest-mcp

by meteoroh

Get stock purchase warnings

tossinvest_get_stock_warnings
Read-onlyIdempotent

Check any stock symbol for active trading warnings and volatility-interruption flags before buying to avoid delisting, overheating, or restricted trades.

Instructions

Get the currently active trading warnings and volatility-interruption (VI) flags for one symbol.

Check this before buying anything unfamiliar — these flags mark designations that restrict or endanger trading.

Args:

  • symbol (string): One symbol.

  • response_format ('markdown' | 'json'): default 'markdown'.

Returns { symbol, count, warnings: [{ warningType, exchange, startDate, endDate }] }, sorted by startDate descending. warningType values:

  • LIQUIDATION_TRADING (정리매매) — delisting liquidation period

  • OVERHEATED (단기과열)

  • INVESTMENT_WARNING (투자경고) / INVESTMENT_RISK (투자위험)

  • VI_STATIC / VI_DYNAMIC / VI_STATIC_AND_DYNAMIC — volatility interruption triggered

  • STOCK_WARRANTS (신주인수권) endDate is null while a designation is still open-ended.

An existing symbol with no active warnings returns count 0 and an empty list — that is a clean result, not an error. VI flags update within seconds; exchange designations update on a daily batch.

Errors: 404 stock-not-found when the symbol does not exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesStock symbol. KRX: 6 digits (e.g. '005930' for Samsung Electronics). US: ticker (e.g. 'AAPL').
response_formatNoOutput format: 'markdown' for a compact human-readable summary, 'json' for the complete raw payload.markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
symbolYes
warningsYesActive warnings, newest first. Empty when the symbol has none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

The description communicates the read-only, idempotent nature beyond the annotations by detailing the expected empty-result behavior, the 404 stock-not-found error, and the update frequency. No hidden side effects or contradictions exist.

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 well-organized with a front-loaded purpose, followed by parameters, return shape, warning enums, edge cases, and errors. Every sentence adds value, and the bullet-style layout makes it easy to scan.

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 provided output schema information, the description fully documents the return structure, all warningType values, the meaning of null endDate, the empty-list success case, and the error condition. No material gaps remain for an agent to invoke and interpret the tool correctly.

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?

The schema already covers both parameters with format examples and enum values. The description adds practical meaning by explaining the response_format choice as compact markdown versus complete raw JSON, which goes slightly beyond the schema.

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 retrieves active trading warnings and volatility-interruption flags for a single stock symbol, framing it as a pre-purchase safety check. This distinguishes it from sibling tools that handle prices, orders, or market data.

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 explicitly advises checking this tool before buying unfamiliar stocks and clarifies that an empty warning list is a valid result, not an error. It also notes the update cadence for VI flags versus exchange designations, giving the agent concrete timing context.

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