Skip to main content
Glama
Sign In

LastLook Data

by io.github.zev-lll
OverviewDiscussionsAdmin

Get Current FRED Series Value

get_current_value
Read-onlyIdempotent

Returns only the single most recent value for any supported FRED series. Cheaper than get_series ($0.01 vs $0.05). Use this when you need just the latest reading — e.g. current CPI, unemployment rate, mortgage rate. Use get_series instead when you need historical observations. Price: $0.01 USDC per call via x402 (Base or Solana).

Input Schema

NameRequiredDescriptionDefault
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. Changed2 schema fields changed
    • changedInput schema / properties / series_id / description
      Previous value: -"FRED series ID e.g. CPIAUCSL, UNRATE, MORTGAGE30US, DGS10, DCOILWTICO, SAHMREALTIME"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": "Most recent observed value",
-      "type": "string"
-    }
-  },
-  "required": [
-    "series_id",
-    "label",
-    "value",
-    "date"
-  ],
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and open-world behavior. The description adds cost and payment details ($0.01 USDC via x402 on Base or Solana), which an agent needs before invoking. It does not describe the return shape, such as whether the observation date or units are included.

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 text is short and front-loaded with purpose, and every sentence earns its place: purpose, cost comparison, when to use, alternative, and price.

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?

It is mostly complete for a simple one-parameter read tool with rich annotations. The lack of an output schema leaves the return format (value, date, units) undocumented. Routing among many overlapping siblings is only partly addressed.

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 enum plus its description already explain series_id well. The description's examples (CPI, unemployment, mortgage rate) add a little mapping help but little beyond the schema.

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?

It names a specific action and resource: the single most recent value for a supported FRED series. It separates itself from get_series by contrasting latest-only with historical 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?

It says when to use the tool (latest reading, with examples) and when to use get_series instead (historical data). It gives no guidance against close siblings such as get_treasury_yield_current, get_value_by_date or the bundle tools, which overlap heavily with this one.

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