FXMacroData

Search the Connected Catalogue

catalogue_search

Read-only

Find public macro indicator series, publishers, explicit country links or organisation references. Search by text or filter by currency, country code, or publisher ID. Empty results do not establish missing data coverage. Results include stable IDs and exact next-tool arguments; no observation values. Organisation lookup requires two search characters and returns up to ten references. Access: public catalogue metadata, no API key required.

Input Schema

Name	Required	Description	Default
`kind`	No	Node category: series, publisher, country or organisation.	series
`limit`	No	Maximum results per page, 1-50.
`query`	No	Search text, at most 120 characters, e.g. inflation; empty text uses filters only.
`cursor`	No	Opaque next_cursor from the preceding result with unchanged filters; omit for page one.
`country`	No	Two-letter country code from the catalogue, e.g. AU.
`currency`	No	Lowercase ISO 4217 currency code, e.g. usd.
`publisher`	No	Exact publisher ID from a catalogue result; omit for all publishers.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedNov 5, 2026

removedInput schema / properties / country / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / country / default
```
Removed value: -null
```

addedInput schema / properties / country / description

Added value: +"Two-letter country code from the catalogue, e.g. AU."

addedInput schema / properties / country / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedInput schema / properties / currency / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / currency / default
```
Removed value: -null
```

addedInput schema / properties / currency / description

Added value: +"Lowercase ISO 4217 currency code, e.g. usd."

addedInput schema / properties / currency / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedInput schema / properties / cursor / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / cursor / default
```
Removed value: -null
```

addedInput schema / properties / cursor / description

Added value: +"Opaque next_cursor from the preceding result with unchanged filters; omit for page one."

addedInput schema / properties / cursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```

addedInput schema / properties / kind / description

Added value: +"Node category: series, publisher, country or organisation."

addedInput schema / properties / limit / description
```
Added value: +"Maximum results per page, 1-50."
```

removedInput schema / properties / publisher / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / publisher / default
```
Removed value: -null
```

addedInput schema / properties / publisher / description

Added value: +"Exact publisher ID from a catalogue result; omit for all publishers."

addedInput schema / properties / publisher / type
```
Added value: +[
+  "string",
+  "null"
+]
```

addedInput schema / properties / query / description

Added value: +"Search text, at most 120 characters, e.g. inflation; empty text uses filters only."

removedInput schema / title

Removed value: -"catalogue_searchArguments"

AddedNov 2, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the read-only/open-world annotations, the description adds important behavioral context: access is public with no API key, empty results do not imply missing coverage, organisation lookup returns at most ten references, and results contain stable IDs plus exact next-tool arguments. It also warns that no observation values are returned, which prevents misuse for data retrieval.

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?

The description is compact and front-loaded, starting with the core purpose and then layering in search modes, empty-result caveats, result contents, and access constraints. Every sentence contributes operational value without repetition.

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 has seven parameters, an output schema, and explicit annotations, and the description supplies the remaining operational context an agent needs: public access, no API key, no observation values, stable IDs, exact next-tool arguments, and an important empty-results caveat. Nothing essential for correct selection or invocation appears to be missing.

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 all seven parameters are already documented in the input schema. The description reinforces text search and filter usage, and mentions the two-character organisation query constraint, but adds little parameter-level detail beyond the schema.

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 opens with a specific verb and resource scope: find public macro indicator series, publishers, country links, or organisation references. It clearly separates catalogue metadata search from observation retrieval by stating results include IDs and next-tool arguments but no observation values.

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?

It explains that users can search by text or filter by currency, country code, or publisher ID, and notes the two-character requirement for organisation lookup. It provides clear usage context but does not explicitly route the agent away from sibling tools such as organisation_search or indicator_query.

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

All FXMacroData tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.