Skip to main content
Glama

Bifrost K-Finance & x402 Alpha

kr_disclosure_radar

[$0.06 USDC] Korean corporate regulatory disclosure radar (FSS OpenDART) translating KRX filings into English alpha signals: treasury buybacks, supply contracts, 5% stake flows, and CB/rights dilution alerts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kr_disclosure_radar"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLookback window in days (1-30)
headlinesNoOptional Korean filing titles to classify into English signals
stock_codeNo6-digit KRX stock ticker (e.g. 005930 Samsung Electronics, 000660 SK Hynix) or ALL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It discloses the upstream source (FSS OpenDART), the Korean-to-English translation behavior, and even the $0.06 USDC cost, which is genuinely useful for a spending agent. However, it says nothing about read-only semantics, output shape, latency, rate limits, or what happens on missing/unknown tickers.

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?

One dense, front-loaded sentence that puts the price tag and the core purpose first, then the signal categories. Every clause carries information; the only mild cost is the 'radar' metaphor, which does not by itself clarify the return format.

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

Completeness3/5

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

For a 3-parameter, zero-required-parameter tool with full schema coverage and no output schema, the description does tell an agent what kinds of signals come back. The notable gap is default behavior: with no required parameters, the description never says what happens when it is called with no arguments or with only stock_code.

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%, so all three parameters (days, headlines, stock_code) are already documented in the schema, including the 1-30 range and the 'ALL' sentinel. The description adds no parameter-level meaning beyond that, so the baseline 3 is appropriate.

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 specific resource and outcome: it reads FSS OpenDART Korean corporate filings and converts KRX disclosures into English alpha signals, enumerating the categories (buybacks, supply contracts, 5% stake flows, CB/rights dilution). This differentiates it in substance from siblings like kr_catalyst_brief and kr_macro_pulse, though it never names them or contrasts scopes explicitly.

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

Usage Guidelines3/5

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

Usage is only implied by the enumerated signal categories - an agent can infer it should call this when tracking Korean disclosure-driven catalysts, but there is no explicit when-to-use, when-not-to-use, or alternative-selection guidance against kr_catalyst_brief or kr_macro_pulse.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.