Skip to main content
Glama

대출금리 조회

loan_interest_rate
Read-only

Daily fixed base rates and yields by loan term for the requested business day. 대출기간별 고정기준금리와 유통수익률을 일자별로 조회합니다. date(YYYYMMDD)를 생략하면 오늘이고, 영업일 기준이며 비영업일이면 직전 영업일 고시를 돌려주고 as_of_date 로 실제 고시일을 알립니다. 응답은 date·as_of_date·count·rates(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": "loan_interest_rate"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description still adds real behavior beyond them: non-business-day fallback to the most recent prior business-day quote, the as_of_date field that reports the actual published date, and a per-call cost of 5 points. It omits any discussion of pagination or rate-limit throttling, but the cost disclosure covers the main operational constraint.

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 what the tool returns, followed by the date default, business-day semantics, and response shape, so the agent can stop reading early if it only needs purpose. The full English/Korean duplication makes it longer than strictly necessary, but each paragraph carries distinct information.

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 enumerating the response fields (date, as_of_date, count, rates with term and rate). For a one-parameter read-only lookup, defaults, calendar behavior, return shape, and cost are all covered.

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 100% with a single optional date parameter already documented in the schema, so the baseline is 3. The description goes past the schema by explaining that the returned data is aligned to the business-day calendar and that as_of_date reveals the actual quote date, which changes how an agent should interpret the parameter's effect.

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 opening sentence names a specific resource and verb: daily fixed base rates and yields by loan term for a given business day, mirrored in Korean as 대출기간별 고정기준금리와 유통수익률. That scoping ('by loan term', 'loan') reasonably separates it from siblings like intl_interest_rate and exchange_rate, though no sibling is named 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?

Guidance is present for how to call it (omit date to get today, business-day basis, non-business days return the prior business day's quote) but there is no statement of when to prefer this over intl_interest_rate or other rate tools, and no exclusions are given.

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.