Skip to main content
Glama
Sign In

LastLook Data

by io.github.zev-lll
OverviewDiscussionsAdmin

Get FRED Series Value by Date

get_value_by_date
Read-onlyIdempotent

Returns the value of any supported FRED series for a specific date. Business days only. Use YYYY-MM-DD format. Price: $0.01 USDC per call via x402 (Base or Solana).

Input Schema

NameRequiredDescriptionDefault
dateYesDate in YYYY-MM-DD format, e.g. 2026-05-09
series_idYesFRED series ID. Use IORB for Interest on Reserve Balances, EFFR for Effective Fed Funds Rate, MORTGAGE30US for 30-yr mortgage rate, SAHMREALTIME for Sahm Rule, etc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / date / description
      Previous value: -"Date in YYYY-MM-DD format e.g. 2026-01-15"New value: +"Date in YYYY-MM-DD format, e.g. 2026-05-09"
    • changedInput schema / properties / series_id / description
      Previous value: -"FRED series ID"New value: +"FRED series ID. Use IORB for Interest on Reserve Balances, EFFR for Effective Fed Funds Rate, MORTGAGE30US for 30-yr mortgage rate, SAHMREALTIME for Sahm Rule, etc."
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "date": {
-      "description": "Date of the observation (YYYY-MM-DD)",
-      "type": "string"
-    },
-    "label": {
-      "description": "Human-readable series name",
-      "type": "string"
-    },
-    "series_id": {
-      "description": "FRED series identifier",
-      "type": "string"
-    },
-    "value": {
-      "description": "Observed value on the requested date",
-      "type": "string"
-    }
-  },
-  "required": [
-    "series_id",
-    "label",
-    "value",
-    "date"
-  ],
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the tool read-only, idempotent, open-world, and non-destructive. The description adds valuable operational context beyond annotations: business-days-only behavior and the $0.01 USDC payment requirement via x402.

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?

Four short sentences front-load the purpose, then add only necessary constraints: business days, date format, and cost. There is no wasted language.

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 simple two-parameter read tool with full schema coverage and annotations, the description is mostly complete. The main remaining gap is that it does not explain the return format or behavior for non-business days or unavailable dates.

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%, and the schema already documents both parameters, including the date format and the full series_id enum. The description restates the date format but adds no additional parameter semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: returns the value of a supported FRED series for a specific date. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as get_current_value or get_series.

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?

It provides implied usage guidance by saying the tool is for a specific date and that only business days are supported. However, it does not state when to use this instead of get_current_value, get_series, or other date-specific siblings.

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

All LastLook Data toolsInspect
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.

Resources