Fetches current foreign exchange rates with USD as base for 16 major currencies (EUR, GBP, JPY, CAD, AUD, CHF, CNY, INR, MXN, BRL, KRW, SGD, HKD, SEK, NOK, NZD). Source: Frankfurter (ECB-based). Cache TTL 5min. Use for currency conversion or FX-aware decisions.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is known. The description adds valuable context about the data source (Frankfurter/ECB) and caching behavior (TTL 5min), which helps the agent understand freshness and reliability. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the main function, and includes additional details (source, TTL, use case) with no redundancy or fluff. Every sentence earns its place and is appropriately sized for a simple tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, read-only tool with no output schema, the description is complete. It covers what is fetched, the exact currencies, the source, cache behavior, and intended use. No major information gaps remain.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the schema covers 100%. According to the rubric, a baseline of 4 is appropriate for no-parameter tools. The description does not need to explain parameters; it instead provides the currency list, which is output-related but still relevant context. Baseline of 4 is justified.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool fetches current foreign exchange rates with USD as base, lists the 16 major currencies, and specifies the source. This distinguishes it from sibling tools like tf_btc_price (crypto) and tf_economic_data (broader economics). The verb 'Fetches' is specific and the resource is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description ends with 'Use for currency conversion or FX-aware decisions,' providing a clear context for when to use the tool. However, it does not explicitly name alternative tools or state when not to use it, so it lacks explicit exclusions. The guidance is clear but not fully contrasting with siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clearly distinct purposes (e.g., tf_btc_price vs tf_fear_greed), but there is some overlap between free and premium aggregated tools (e.g., tf_briefing, tf_premium_briefing, tf_premium_agent_context). However, descriptions explicitly differentiate them by content and cost.
All tools follow a consistent pattern: 'tf_' prefix (with 'tf_premium_' for premium ones) and snake_case. Names are descriptive and predictable, e.g., tf_btc_price, tf_earthquakes, tf_premium_macro.
27 tools is on the high side, but the server covers a broad domain (crypto, finance, earthquakes, AI trends, payment system, etc.). Each tool serves a specific purpose, so the count is borderline acceptable but feels slightly heavy.
The tool surface covers a wide range of data feeds: crypto, forex, macro indicators, earthquakes, HN, HuggingFace, prediction markets, payment system, and service status. Minor gaps exist (e.g., no dedicated stock prices tool beyond premium macro, no weather), but overall it's comprehensive for a terminal feed.
