Skip to main content
Glama
korea-finance-factcheck

korea-finance-factcheck

check_market_numbers

Verifies market figures in Korean finance articles against official US Treasury, KOSPI close, Bank of Korea ECOS base rate and FX data, flagging mismatches for the stated article date.

Instructions

미국 국채금리(재무부)와 코스피 종가·한국 기준금리·환율(한국은행 ECOS)을 그날 공식값과 대조한다.

as_of 는 글을 쓴 날(YYYY-MM-DD). 없으면 본문의 '작성: 날짜' 줄, 그것도 없으면 오늘. ECOS 항목은 ECOS_API_KEY 가 필요하다.

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": {
      "text": "<text>"
    },
    "name": "check_market_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
as_ofNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the conditional dependency on ECOS_API_KEY, so the agent knows part of the check may fail without it. It does not describe what the comparison output contains (mismatch report? pass/fail per item?) or failure behavior when the key is absent.

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?

Front-loaded with the resource list, then the parameter rule, then the prerequisite. Three short blocks with no filler; the only weakness is that the as_of fallback chain reads as a run-on rather than a clean conditional.

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 verification tool with no output schema and no annotations, the description covers inputs and prerequisites well but leaves the result shape and per-source failure modes undefined. An agent knows what to send but not what to expect back.

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?

Schema coverage is 0%, so the description must compensate and it largely does: as_of gets format (YYYY-MM-DD) and a full fallback chain for deriving it. The required 'text' parameter is never described, though its meaning is inferable from the 'article body' reference.

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 action (cross-check against official values) and enumerates the exact resources covered: US Treasury yields, KOSPI close, Korean base rate, and FX via ECOS. An agent can see this is a numeric fact-verification tool, though the boundary with check_stock_closes (which also sounds like stock closes) is not spelled out.

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?

Gives a clear resolution rule for as_of (explicit date → '**작성**:' line → today) and notes the ECOS_API_KEY prerequisite, which is useful operational context. However, it never says when to prefer this over check_all or check_stock_closes, nor when not to use it.

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