Skip to main content
Glama

Bifrost K-Finance & x402 Alpha

kr_catalyst_brief

[$0.08 USDC] US-to-Korea cross-border supply chain & catalyst intelligence mapping US tech/industrial tickers (NVDA, MU, TSLA, AAPL, MSFT, LLY, LMT) or themes (HBM, POWER_GRID, DEFENSE) to Tier-1 KRX suppliers and key macro/earnings catalysts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "us_ticker_or_theme": "<us_ticker_or_theme>"
    },
    "name": "kr_catalyst_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_calendarNoInclude upcoming Korea/Global macro & semiconductor catalyst calendar
us_ticker_or_themeYesUS ticker (NVDA, MU, TSLA, AAPL, MSFT, LLY, LMT, AVGO) or theme (HBM, POWER_GRID, DEFENSE, CDMO, EV_BATTERY, SHIPBUILDING)

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?

No annotations are supplied, so the description carries the full burden. It usefully discloses the cost ($0.08 USDC) and the general shape of the output (Tier-1 KRX suppliers plus macro/earnings catalysts), but says nothing about permissions, rate limits, latency, or whether results are cached or time-sensitive.

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?

A single dense sentence that front-loads the price and then the core purpose, with zero filler. It packs tickers and theme tokens inline, which is slightly list-heavy but earns its space.

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 two-parameter tool with no output schema and no annotations, the description covers what is queried and roughly what comes back, which is the minimum needed. It leaves gaps around output structure, whether the calendar flag changes response shape, and how it relates to the sibling macro and disclosure tools.

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%, and the schema already lists tickers, themes, and the include_calendar flag with its own description. The description's parameter mention largely repeats the schema rather than adding format constraints, valid-combination rules, or error behavior.

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?

The description states a specific resource and action: mapping US tickers/themes to Tier-1 KRX suppliers and macro/earnings catalysts. It names concrete inputs (NVDA, HBM, POWER_GRID, DEFENSE) so an agent can immediately judge relevance, though it never explicitly contrasts itself with siblings like kr_macro_pulse or kr_disclosure_radar.

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 implied by the enumeration of accepted ticker and theme inputs, which tells the agent the tool is for cross-border supply-chain lookups. However, there is no explicit when-to-use versus when-not guidance, and no mention of when to prefer kr_macro_pulse or kr_disclosure_radar instead.

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.