FXMacroData

Follow Catalogue Relationships

catalogue_related

Read-only

Follow evidence-linked catalogue relationships from a node ID returned by catalogue_search. Depth is one or two, limit is at most fifty; use the returned cursor for more results. Paths explain recorded metadata relationships, not causality or series equivalence. Retrieval tools enforce their existing data access rules. Access: public metadata relationships, no API key required.

Input Schema

Name	Required	Description
`depth`	No	Relationship traversal depth: 1 (direct) or 2 (one additional hop).
`limit`	No	Maximum results per page, 1-50.
`cursor`	No	Opaque next_cursor from the preceding result with unchanged filters; omit for page one.
`node_id`	Yes	Exact opaque node ID from a catalogue result; do not construct an ID.
`relationship`	No	Optional edge type: published_by, about_country, cites_source or related_series.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedNov 5, 2026

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 / depth / description

Added value: +"Relationship traversal depth: 1 (direct) or 2 (one additional hop)."

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

addedInput schema / properties / node_id / description

Added value: +"Exact opaque node ID from a catalogue result; do not construct an ID."

removedInput schema / properties / relationship / anyOf

Removed value: -[
-  {
-    "enum": [
-      "published_by",
-      "about_country",
-      "cites_source",
-      "related_series"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

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

addedInput schema / properties / relationship / description

Added value: +"Optional edge type: published_by, about_country, cites_source or related_series."

addedInput schema / properties / relationship / enum

Added value: +[
+  "published_by",
+  "about_country",
+  "cites_source",
+  "related_series",
+  null
+]

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

removedInput schema / title

Removed value: -"catalogue_relatedArguments"

AddedNov 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the description's job is to add operational context — and it does: traversal depth bounds, the 50-result cap, cursor-based continuation, and an explicit caveat that returned paths are recorded metadata edges rather than causal or equivalence claims. It also states access policy (public metadata, no API key). Missing only something about failure behavior for invalid or stale node IDs.

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

Conciseness4/5

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

Front-loaded with purpose, then constraints, then the semantic caveat, then access — a logical order with no filler sentences. Slightly dense with semicolon-chained clauses, but every sentence carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 values need not be explained, and annotations cover the safety profile; the description supplies the remaining essentials (entry point, bounds, pagination, interpretation caveat, access). Only minor gaps remain around what a relationship path contains and error conditions.

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%, so every parameter including depth, limit, cursor, node_id and the relationship enum is already documented. The description's parameter remarks (depth one or two, limit at most fifty, reuse the cursor) duplicate the schema rather than adding new meaning. 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 a specific verb and resource ('Follow evidence-linked catalogue relationships') and ties the input to a named sibling ('node ID returned by catalogue_search'). This distinguishes it clearly from catalogue_search and the many task/tool siblings that do not traverse graph edges.

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?

Explicitly frames the entry condition (you need a node ID from catalogue_search) and warns about interpretation ('not causality or series equivalence'), which is real usage guidance. It stops short of an explicit when-not-to-use statement or naming an alternative traversal tool, so it is a strong 4 rather than a 5.

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.