Skip to main content
Glama

bifrost-kfinance-mcp

kr_macro_pulse

[$0.05 USDC] Bank of Korea (ECOS) macro & FX pulse returning live BOK base rate, USD/KRW and JPY/KRW exchange rates, KTB 3Y/10Y sovereign yields, term spread in bps, CPI, and exporter regime.

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_macro_pulse"
  }
}

Input Schema

NameRequiredDescriptionDefault
fx_pairsNoRequested FX pairs among USDKRW, JPYKRW, EURKRW, CNYKRW
include_yield_curveNoInclude KTB 3Y/10Y yields and 10Y-3Y spread in bps

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real context: the tool is metered at $0.05 USDC and sources live BOK/ECOS data. It does not state whether access is read-only, whether credentials or rate limits apply, or what happens when a requested pair or series is unavailable, which is a meaningful gap for an unannotated tool.

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 cost then purpose and then the payload. Every clause is informative, with only minor redundancy between the listed contents and what the parameters already imply.

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

Completeness4/5

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

No output schema exists, so the description is responsible for conveying return values, and it does so field by field, which is the main thing an agent needs. Missing usage guidance and error/empty-result behavior are the remaining shortfalls for a tool of this simplicity.

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 coverage is 100%, so both parameters are already documented in the schema, including the accepted pair values. The description echoes some of that content (USD/KRW, JPY/KRW, yields and spread) but adds no formatting, default, or omission semantics beyond it, so the baseline applies.

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 names a concrete source (Bank of Korea ECOS) and enumerates the exact data returned: base rate, USD/KRW and JPY/KRW, KTB 3Y/10Y yields, term spread in bps, CPI, and exporter regime. That is enough to distinguish it from siblings like kr_catalyst_brief or kr_disclosure_radar, which are clearly not macro/FX reads, though it never states the contrast explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no alternative tool is named. The only steer is implicit in the enumerated payload, leaving the agent to infer that this is the macro/FX lookup versus the catalyst or disclosure tools.

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.

Resources