Skip to main content
Glama

Treasury Fiscal

by io.github.pipeworx-io

Treasury Exchange Rates

treasury_exchange_rates
Read-onlyIdempotent

Get official US Treasury exchange rates used for government currency conversions. Pass a country name for one country's rate; omit it for the most recent rates across all countries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of records to return (default 12)
countryNoCountry name (e.g., "China", "Mexico", "Japan", "Canada"). Treasury indexes by country, not currency: the euro is "Euro Zone" (common aliases like "Eurozone"/"EUR" are accepted), and there is no United States row because these are rates from the dollar. Omit for the latest rates across all countries.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoPresent when the live API was unreachable and the mirror answered
countYes
sourceNolive or mirror
countryNoEcho of the country filter; ABSENT when the caller omitted it and got rates across all countries
recordsYes
descriptionYes
mirror_fetched_atNoTimestamp of the underlying rate data

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / properties / mirror_fetched_at / description
      Previous value: -"Present when served from the daily mirror"New value: +"Timestamp of the underlying rate data"
  2. Changed16 schema fields changed
    • addedOutput schema / description
      Added value: +"US Treasury exchange rates. Indexed by COUNTRY, not currency — the euro is filed under \"Euro Zone\", and there is no United States row because these are rates from the dollar."
    • removedOutput schema / properties / count / description
      Removed value: -"Number of records returned"
    • changedOutput schema / properties / country / description
      Previous value: -"Country name requested"New value: +"Echo of the country filter; ABSENT when the caller omitted it and got rates across all countries"
    • changedOutput schema / properties / country / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / description / description
      Removed value: -"Description of the data"
    • addedOutput schema / properties / mirror_fetched_at
      Added value: +{
+  "description": "Present when served from the daily mirror",
+  "type": "string"
+}
    • addedOutput schema / properties / note
      Added value: +{
+  "description": "Present when the live API was unreachable and the mirror answered",
+  "type": "string"
+}
    • removedOutput schema / properties / records / description
      Removed value: -"Exchange rate records"
    • removedOutput schema / properties / records / items / properties / country / description
      Removed value: -"Country name"
    • removedOutput schema / properties / records / items / properties / currency / description
      Removed value: -"Currency code"
    • removedOutput schema / properties / records / items / properties / effective_date / description
      Removed value: -"Effective date of the rate"
    • removedOutput schema / properties / records / items / properties / exchange_rate / description
      Removed value: -"Exchange rate value"
    • changedOutput schema / properties / records / items / properties / exchange_rate / type
      Previous value: -"number"New value: +[
+  "number",
+  "string"
+]
    • removedOutput schema / properties / records / items / properties / record_date / description
      Removed value: -"Date of the record"
    • addedOutput schema / properties / source
      Added value: +{
+  "description": "live or mirror",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "description",
-  "country",
-  "count",
-  "records"
-]New value: +[
+  "description",
+  "count",
+  "records"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / country / description
      Previous value: -"Country name (e.g., \"China\", \"Mexico\", \"Japan\", \"Canada\")"New value: +"Country name (e.g., \"China\", \"Mexico\", \"Japan\", \"Canada\"). Treasury indexes by country, not currency: the euro is \"Euro Zone\" (common aliases like \"Eurozone\"/\"EUR\" are accepted), and there is no United States row because these are rates from the dollar. Omit for the latest rates across all countries."
  4. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "country"
-]New value: +[]
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of records returned",
+      "type": "number"
+    },
+    "country": {
+      "description": "Country name requested",
+      "type": "string"
+    },
+    "description": {
+      "description": "Description of the data",
+      "type": "string"
+    },
+    "records": {
+      "description": "Exchange rate records",
+      "items": {
+        "properties": {
+          "country": {
+            "description": "Country name",
+            "type": "string"
+          },
+          "currency": {
+            "description": "Currency code",
+            "type": "string"
+          },
+          "effective_date": {
+            "description": "Effective date of the rate",
+            "type": "string"
+          },
+          "exchange_rate": {
+            "description": "Exchange rate value",
+            "type": "number"
+          },
+          "record_date": {
+            "description": "Date of the record",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "description",
+    "country",
+    "count",
+    "records"
+  ],
+  "type": "object"
+}
  6. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "country": "China",
+    "limit": 12
+  },
+  {
+    "country": "Japan",
+    "limit": 24
+  }
+]
  7. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the 'government currency conversions' context and the dual-mode behavior, but does not disclose any additional behavioral details (e.g., rate limits, response format, or errors). Given the annotations, the description's value is moderate, so a 3 is fair.

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?

Two sentences with no filler. The purpose is front-loaded, followed by the two usage modes. Every word contributes to clarity, making this an exemplary concise definition.

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?

The tool is simple (2 optional params, 0 required), and the schema covers both parameters thoroughly. The output schema exists, so return values need no description. The description covers the primary use cases and is complete given the annotations and schema, leaving no gaps for correct invocation.

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 description coverage is 100%, with detailed explanations for both parameters. The country field is especially well-documented with aliases and the no-US-row note. The description repeats the 'omit for all countries' guidance already in the schema, adding minimal extra value. With high schema coverage, the baseline of 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?

The description states a specific verb ('Get') and resource ('official US Treasury exchange rates') with the purpose ('used for government currency conversions'). It clearly distinguishes this from other treasury tools (interest rates, debt, etc.) by focusing on exchange rates, and the two invocation modes (with/without country) are explicitly described.

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?

The description clearly explains when to pass a country name versus omit it for all countries, which is the core usage guidance. However, it does not explicitly compare against sibling tools (e.g., treasury_avg_interest_rates), leaving the agent to infer which tool to choose. Still, the purpose is so specific that usage is largely self-evident, so a 4 is appropriate.

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

All Treasury Fiscal toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Most of the surface is dominated by overlapping meta-tools (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) plus paired helpers (discover_tools/suggest_questions, ai_visibility_check/scan_competitor_ai_presence), so an agent can easily pick the wrong one. The seven treasury_* tools are clearly distinct, but they are a small island in a much larger ambiguous set.

Naming Consistency3/5

Names are broadly snake_case and family-prefixed (treasury_*, polymarket_*, pipeworx_*), which helps, but the pattern is not consistently verb_noun: ask_pipeworx, bet_research, entity_profile, deep_research, search_within, and recent_changes mix verb, noun, and product-specific naming styles. Within families it is readable, but across the whole set it is inconsistent.

Tool Count2/5

37 tools is too many for a server whose label is 'Treasury Fiscal'; only about six tools are treasury-specific and the rest are unrelated research, betting, memory, and subscription utilities. This is well into the 25+ heavy range and would make tool selection expensive and error-prone.

Completeness2/5

For a Treasury/Fiscal server the surface is thin: debt, receipts, customs duty, average rates, exchange rates, and net cost cover only a slice of Treasury data. Missing obvious components such as daily yield curves, auction calendars/results, federal outlays/spending by agency or function, and tax or appropriations data; the broad ask_pipeworx router softens but does not fill these as first-class tools.

Resources