tr-macro-mcp

Overview Schema Source Related Servers Discussions Admin

get_fx_rate

Retrieve the official TCMB indicative exchange rate for a currency against the Turkish lira on a given date, with no API key. If no bulletin exists, returns status and nearest earlier bulletin date.

Instructions

Official TCMB indicative exchange rate of a currency against the Turkish lira (TRY per 1 unit) for a date. Works without any API key.

TCMB publishes one bulletin per business day around 15:30 Istanbul time. If no bulletin exists for the date (weekend, holiday, not yet published), status is 'not_published' and no rate is returned; 'nearest_earlier_bulletin' names the closest earlier date with a bulletin, which you may query explicitly. Never present that date's rate as the requested date's rate. Cite the returned citation (bulletin URL and number).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No	Bulletin date (YYYY-MM-DD). Omit for the latest bulletin.
`currency`	Yes	ISO code, e.g. 'USD', 'EUR', 'GBP', 'JPY', 'XDR'.
`rate_type`	No	Which rate goes into 'value'. All four are in 'quote'.	forex_buying

Output Schema

TableJSON Schema

Name	Required	Description
`notes`	No
`quote`	No
`value`	Yes	The requested rate_type, per 1 unit, in TRY.
`status`	Yes
`citations`	Yes
`rate_type`	Yes
`bulletin_no`	No
`bulletin_date`	Yes	Date of the bulletin the rates come from. Equals requested_date when status=ok.
`requested_date`	Yes	None means 'latest bulletin'.
`available_currencies`	No
`nearest_earlier_bulletin`	No	Only for status=not_published: the closest earlier date that has a bulletin. Its rates are NOT the requested date's rates.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 3, 2026

TDQS

A4.9/5.0

Behavior5/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 and does so richly: authentication-free access, publication cadence and time zone, the 'not_published' status contract, the 'nearest_earlier_bulletin' fallback field, and a citation obligation. These are exactly the behavioral traits an agent needs before calling.

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?

Front-loaded with the core purpose, then edge-case handling and a citation rule. Every sentence earns its place; nothing is padding.

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 an output schema present, return shape needn't be restated, and the description still covers the failure mode, the fallback field, and the citation requirement. Nothing an agent needs to call this correctly is missing.

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 description coverage is 100%, so the schema already documents all three parameters (date default, ISO currency codes, rate_type enum). The description adds value beyond that by clarifying the value's direction and units ('TRY per 1 unit') and the bulletin-date semantics that the schema only implies.

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 a specific verb+resource+scope: 'Official TCMB indicative exchange rate of a currency against the Turkish lira (TRY per 1 unit) for a date.' This is unambiguous and distinct from every sibling (series, documents, comparisons), none of which touch rates.

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

Usage Guidelines5/5

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

Gives explicit when-to-use context (works without an API key; one bulletin per business day around 15:30 Istanbul) and clear when-not behavior: weekends/holidays/unpublished dates yield status 'not_published' with no rate. It further instructs the agent to query 'nearest_earlier_bulletin' explicitly and warns never to present that date's rate as the requested one.

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

Deploy Server