Skip to main content
Glama

Economic Data Changes

econ_changes

Retrieve recent updates to economic indicators from FRED, BLS, and BEA by specifying a timestamp. Track changes to datasets with a pay-per-query model.

Instructions

Get recent changes to economic data since a given timestamp. Cost: $0.005 per query. Source: FRED, BLS, BEA.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinceYesISO 8601 timestamp to get changes since (e.g. 2026-03-01T00:00:00Z)
limitNoMaximum results (default 50)

Implementation Reference

  • The 'registerEconTools' function is called from src/index.ts, and within it, server.registerTool('econ_changes', ...) registers the tool. The handler, schema, and registration are all in one block.
    // ── Change feed ───────────────────────────────────────────────────────
    
    server.registerTool(
      "econ_changes",
      {
        title: "Economic Data Changes",
        description:
          "Get recent changes to economic data since a given timestamp. " +
          "Cost: $0.005 per query. Source: FRED, BLS, BEA.",
        inputSchema: {
          since: z
            .string()
            .describe("ISO 8601 timestamp to get changes since (e.g. 2026-03-01T00:00:00Z)"),
          limit: z
            .number()
            .int()
            .min(1)
            .max(100)
            .optional()
            .describe("Maximum results (default 50)"),
        },
      },
      async ({ since, limit }) => {
        const res = await apiGet<EconQueryResponse>("/api/v1/econ/changes", {
          since,
          limit: limit ?? 50,
        });
    
        if (!res.ok) {
          return {
            content: [
              {
                type: "text" as const,
                text: `API error (${res.status}): ${JSON.stringify(res.data)}`,
              },
            ],
            isError: true,
          };
        }
    
        const { count, data } = res.data;
        const warn = stalenessWarning(res);
        const summary = `${warn}Found ${count} economic data change(s) since ${since}.`;
        const json = JSON.stringify(data, null, 2);
    
        return {
          content: [{ type: "text" as const, text: `${summary}\n\n${json}` }],
        };
      },
    );
  • Input schema definition for the econ_changes tool, defining 'since' (required ISO 8601 string) and 'limit' (optional int, 1-100, default 50) parameters.
    {
      title: "Economic Data Changes",
      description:
        "Get recent changes to economic data since a given timestamp. " +
        "Cost: $0.005 per query. Source: FRED, BLS, BEA.",
      inputSchema: {
        since: z
          .string()
          .describe("ISO 8601 timestamp to get changes since (e.g. 2026-03-01T00:00:00Z)"),
        limit: z
          .number()
          .int()
          .min(1)
          .max(100)
          .optional()
          .describe("Maximum results (default 50)"),
      },
    },
  • The async handler function for econ_changes. It calls apiGet to "/api/v1/econ/changes" with 'since' and 'limit' params, handles errors, and returns the data as text content.
    async ({ since, limit }) => {
      const res = await apiGet<EconQueryResponse>("/api/v1/econ/changes", {
        since,
        limit: limit ?? 50,
      });
    
      if (!res.ok) {
        return {
          content: [
            {
              type: "text" as const,
              text: `API error (${res.status}): ${JSON.stringify(res.data)}`,
            },
          ],
          isError: true,
        };
      }
    
      const { count, data } = res.data;
      const warn = stalenessWarning(res);
      const summary = `${warn}Found ${count} economic data change(s) since ${since}.`;
      const json = JSON.stringify(data, null, 2);
    
      return {
        content: [{ type: "text" as const, text: `${summary}\n\n${json}` }],
      };
    },
  • src/index.ts:57-57 (registration)
    Registration call: registerEconTools(server) is invoked in the createMcpServer() function, registering all econ tools including econ_changes on the MCP server.
    registerEconTools(server);
Behavior3/5

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

No annotations provided. The description adds cost per query and data sources (FRED, BLS, BEA) but lacks details on side effects, rate limits, or pagination. It adequately discloses that it is a paid read operation.

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 concise sentences: purpose, cost, sources. No fluff, every sentence adds value.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose, cost, and sources but lacks information about the output format or return structure. Given no output schema, the description should ideally mention what the response looks like. It is adequate for a simple tool but not fully complete.

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?

Input schema has 100% coverage with descriptions for both parameters. The description does not add any additional information about parameters beyond what the schema provides, so baseline 3 applies.

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 clearly states the tool retrieves recent changes to economic data, using a specific verb (Get) and resource (recent changes). It distinguishes from siblings like econ_stats, dex_changes, holder_changes, etc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions cost and data sources but does not explicitly state when to use this tool vs alternatives or provide exclusions. Usage is implied but not guided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/carrierone/verilexdata-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server