Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Macro Indicator List

macrodata_indicators
Read-onlyIdempotent

Search macro-economic indicators by country and keyword, then use the returned indicator_code to fetch data via macrodata. Supports pagination.

Instructions

List macro-economic indicators. Filter by keyword and country (US/CN/HK/EU/JP/SG). Use the returned indicator_code with macrodata. 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 indicators to return (default 100, max 1000).
offsetNoPagination offset, default 0.
countryNoFilter by country code. One of: "US", "CN", "HK", "EU", "JP", "SG". Omit to return all countries.
keywordNoKeyword to search indicator names (e.g. "CPI", "非农", "GDP").

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": {
-    "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"
-    },
-    "list": {
-      "items": {
-        "$ref": "#/$defs/MacroeconomicIndicator"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "list",
-    "count"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.4
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "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"
+    },
+    "list": {
+      "items": {
+        "$ref": "#/$defs/MacroeconomicIndicator"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "list",
+    "count"
+  ],
+  "type": "object"
+}
  4. Addedv0.7.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive. The description adds that it supports pagination and that results feed into macrodata, which is useful context. No contradictions, and no additional behavioral claims beyond annotations.

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?

Three sentences, front-loaded with the core function, and each sentence adds value. No redundancy.

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?

For a read-only list tool with full schema coverage and safety annotations, the description covers filtering, pagination, and downstream usage. The only omission is the generic _jq parameter, which is common across tools and self-explanatory.

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%, and the description highlights keyword, country, and pagination parameters. It adds minimal detail beyond the schema, but the reference to indicator_code clarifies the output's role.

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 the verb 'List' and the resource 'macro-economic indicators', and clarifies it returns indicator codes for use with macrodata. This distinguishes it from the sibling macrodata tool, making its purpose unambiguous.

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 instructs to use the returned indicator_code with macrodata, and describes filtering by keyword and country, plus pagination. This gives clear context on when and how to use it, though it doesn't explicitly contrast with alternative listing tools.

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