Skip to main content
Glama

국제금리 조회

intl_interest_rate
Read-only

Daily international interest rates (overnight RFRs such as SOFR and ESTR, term rates and CIRR) by currency and term. SOFR·ESTR·TONA 등 국제금리와 통화별 중장기 고시 금리를 일자별로 조회합니다. date(YYYYMMDD)를 생략하면 오늘이고, 영업일 기준이며 비영업일이면 직전 영업일 고시를 돌려주고 as_of_date 로 실제 고시일을 알립니다. 응답은 date·as_of_date·count·rates(currency·term·rate) 입니다. [호출당 5포인트]

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": "intl_interest_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo조회 일자 YYYYMMDD (예: 20261114). 생략하면 오늘

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the non-business-day fallback rule, the as_of_date field that reports the actual quote date, the full response shape, and a per-call cost of 5 points. These are exactly the behavioral traits annotations cannot express.

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?

The content is front-loaded and every element (rate families, default date, business-day fallback, response fields, cost) is useful. The English and Korean sentences largely duplicate each other, which is mild redundancy rather than waste.

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?

With no output schema, the description compensates by listing the returned fields (date, as_of_date, count, rates with currency/term/rate). Combined with the default-date and fallback rules, an agent has everything needed to call and interpret the result.

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% and the single date parameter is already documented with format and default in the schema. The description restates the YYYYMMDD format and the omit-means-today default without adding new semantics, so the baseline 3 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 specific resource (daily international interest rates) and enumerates the concrete rate families covered — overnight RFRs like SOFR/ESTR/TONA, term rates, and CIRR — plus the currency/term dimension. That is enough to separate it from loan_interest_rate and exchange_rate, though it never explicitly contrasts with those siblings.

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?

It gives clear operational context (date omitted means today, business-day basis, non-business days fall back to the prior business day), which tells the agent how to call it. It does not state when to prefer this over loan_interest_rate or exchange_rate, so usage selection is only implied.

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.