Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Macro Indicator Data

macrodata
Read-onlyIdempotent

Retrieve historical observations for a macro-economic indicator by code, with optional date range and pagination for controlled data retrieval.

Instructions

Get historical observations for one macro-economic indicator. Use indicator_code from macrodata_indicators; start_date/end_date accept YYYY-MM-DD. Supports offset/limit pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_jqNoOptional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response.
limitNoMaximum number of data points to return (default 100, max 100).
offsetNoPagination offset for historical data points, default 0.
end_dateNoLatest release date to include (YYYY-MM-DD, e.g. `"2024-12-31"`).
start_dateNoEarliest release date to include (YYYY-MM-DD, e.g. `"2024-01-01"`).
indicator_codeYesIndicator code from `macrodata_indicators`, e.g. `"30771718"`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.12.0
    • addedInput schema / properties / _jq / description
      Added value: +"Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response."
    • removedInput schema / properties / limit / format
      Removed value: -"int32"
    • removedInput schema / properties / offset / format
      Removed value: -"int32"
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "MacroeconomicDataPoint": {
-      "properties": {
-        "actual_value": {
-          "type": "string"
-        },
-        "forecast_value": {
-          "type": "string"
-        },
-        "period": {
-          "type": "string"
-        },
-        "previous_value": {
-          "type": "string"
-        },
-        "release_at": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "unit": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "period",
-        "actual_value",
-        "previous_value",
-        "forecast_value",
-        "unit"
-      ],
-      "type": "object"
-    },
-    "MacroeconomicIndicator": {
-      "properties": {
-        "country": {
-          "type": "string"
-        },
-        "describe": {
-          "type": "string"
-        },
-        "importance": {
-          "format": "int32",
-          "type": "integer"
-        },
-        "indicator_code": {
-          "type": "string"
-        },
-        "name": {
-          "type": "string"
-        },
-        "periodicity": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "indicator_code",
-        "country",
-        "name",
-        "describe",
-        "periodicity",
-        "importance"
-      ],
-      "type": "object"
-    }
-  },
-  "properties": {
-    "count": {
-      "format": "int32",
-      "type": "integer"
-    },
-    "data": {
-      "items": {
-        "$ref": "#/$defs/MacroeconomicDataPoint"
-      },
-      "type": "array"
-    },
-    "info": {
-      "$ref": "#/$defs/MacroeconomicIndicator"
-    }
-  },
-  "required": [
-    "info",
-    "data",
-    "count"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.4
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "MacroeconomicDataPoint": {
+      "properties": {
+        "actual_value": {
+          "type": "string"
+        },
+        "forecast_value": {
+          "type": "string"
+        },
+        "period": {
+          "type": "string"
+        },
+        "previous_value": {
+          "type": "string"
+        },
+        "release_at": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "unit": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "period",
+        "actual_value",
+        "previous_value",
+        "forecast_value",
+        "unit"
+      ],
+      "type": "object"
+    },
+    "MacroeconomicIndicator": {
+      "properties": {
+        "country": {
+          "type": "string"
+        },
+        "describe": {
+          "type": "string"
+        },
+        "importance": {
+          "format": "int32",
+          "type": "integer"
+        },
+        "indicator_code": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "periodicity": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "indicator_code",
+        "country",
+        "name",
+        "describe",
+        "periodicity",
+        "importance"
+      ],
+      "type": "object"
+    }
+  },
+  "properties": {
+    "count": {
+      "format": "int32",
+      "type": "integer"
+    },
+    "data": {
+      "items": {
+        "$ref": "#/$defs/MacroeconomicDataPoint"
+      },
+      "type": "array"
+    },
+    "info": {
+      "$ref": "#/$defs/MacroeconomicIndicator"
+    }
+  },
+  "required": [
+    "info",
+    "data",
+    "count"
+  ],
+  "type": "object"
+}
  4. Addedv0.7.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds useful behavioral context beyond those hints: pagination via offset/limit and the requirement to source indicator_code from the sibling tool, so the agent knows the expected input relationship.

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 three short, purposeful sentences with the core purpose front-loaded. Each sentence earns its place by covering the tool's purpose, required-parameter sourcing, date format, and pagination behavior.

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?

For a read-only, idempotent tool with full schema documentation, the description covers what is needed to invoke it correctly: which indicator to fetch, where the code comes from, date formatting, and pagination. The lack of an output schema is not a significant gap here because the returned resource is described as historical observations.

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 the schema already documents every parameter. The description largely restates what is already in the schema ('start_date/end_date accept YYYY-MM-DD', 'offset/limit pagination'), adding only minimal extra meaning beyond the structured fields.

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: 'Get historical observations for one macro-economic indicator.' This clearly distinguishes the tool from the sibling macrodata_indicators, which lists indicator metadata rather than observations.

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 tells the agent exactly where to obtain the required parameter ('Use indicator_code from macrodata_indicators') and specifies date formats and pagination support. It does not explicitly state exclusions or alternative tools, but the usage context is clear.

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

Deploy Server

Other Tools