Skip to main content
Glama

The Korean Today (코리안투데이)

KRW exchange rates (public sources)

krw_exchange_rates
Read-onlyIdempotent

Today's base rates in South Korean won (KRW per unit) for about 43 currencies, from public official sources only: Export-Import Bank of Korea and Bank of Korea (ECOS). Updated each Seoul business-day morning. Indicative, not for transactions. Each result includes the source page URL and an attribution line.

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

Input Schema

NameRequiredDescriptionDefault
currenciesNoISO codes like USD, JPY, EUR. Empty = all available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, and the description adds genuinely new behavior: update cadence tied to Seoul business days, authoritative sourcing, an accuracy disclaimer, and the fact that responses carry a source URL and attribution line. Minor tension exists between 'public official sources' and openWorldHint=false, but the text frames these as data origins rather than live external calls, so it does not read as a contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with what the tool returns and its unit, followed by sourcing, freshness, and the disclaimer. Every sentence contributes distinct information — scope, provenance, cadence, limitation, response shape — with no restated title or filler.

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?

For a one-optional-parameter read tool with rich annotations and no output schema, the description covers everything an agent needs: unit basis, coverage, filtering behavior, freshness, and what the returned records contain. The stated response fields (source URL, attribution) compensate for the absent output schema.

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 the currencies array, ISO-code format, and 'empty = all available' are already documented in structured data. The description adds only the approximate size of the full set (~43 currencies), which helps an agent decide whether to filter but is not substantive new semantics. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the resource (KRW base rates per unit), the scope (~43 currencies), the data providers by name, and the freshness window. An agent immediately knows this returns FX rates rather than articles, and the 'public official sources only' clause distinguishes the dataset from any generic rate lookup.

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

Usage Guidelines4/5

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

Provides clear context for use (today's indicative base rates, updated each Seoul business-day morning) and a meaningful exclusion: 'Indicative, not for transactions.' It does not name an alternative tool or discuss what to do when a rate is missing, but for a single-purpose lookup the guidance is sufficient.

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