Skip to main content
Glama

SiteCheck

by io.github.bck-stack
OverviewDiscussionsAdmin

Macro

macro
Read-only

Official rate and macro series in one call, by name: fed_funds, us_cpi, us_core_cpi, us_unemployment, us_10y, us_2y, us_mortgage_30y, us_gdp, wti_oil, brent_oil, henry_hub_gas, us_house_price_index, ecb_deposit_rate, ecb_main_refi_rate and euro_area_hicp. Latest value, change vs previous and vs a year earlier, and observations. Up to 6 series. FRED (US public domain), the ECB Data Portal and Eurostat. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Input Schema

NameRequiredDescriptionDefault
fromNoOnly observations from this date (YYYY-MM-DD) on
limitNoObservations per series, 1-120, default 12
seriesYesUp to 6 series names, comma-separated: fed_funds, us_cpi, us_core_cpi, us_unemployment, us_10y, us_2y, us_mortgage_30y, us_gdp, wti_oil, brent_oil, henry_hub_gas, us_house_price_index, ecb_deposit_rate, ecb_main_refi_rate, euro_area_hicp

Output Schema

NameRequiredDescriptionDefault
seriesNo
sourceNo
licenseNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "checkedAt": {},
+    "license": {},
+    "series": {},
+    "source": {}
+  },
+  "type": "object"
+}
  2. Added

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses pricing ($0.002 USDC per successful call via x402 on Base, Solana or Arc), that failed calls are not charged, the data provenance and licensing (FRED public domain, ECB, Eurostat), and the batch cap of 6 series. This is exactly the extra context annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the capability, then output shape, then commercial/source details — every sentence carries information. The long comma-separated series list duplicates the schema enumeration and slightly bloats the text, keeping it below a 5.

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?

An output schema exists, yet the description still summarizes the return shape (latest value, change vs previous and vs a year earlier, observations). Combined with provenance, pricing and the batch limit, nothing material needed to invoke the tool correctly is missing.

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 from, limit and series. The description only restates the series names and the 6-series cap, which duplicates the schema rather than adding format or defaulting nuance, so the baseline 3 applies.

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 concrete resource (official rate and macro series from FRED, ECB Data Portal, Eurostat) and enumerates the exact series accepted, so an agent knows precisely what it gets. It does not differentiate from the sibling econ_indicator, which is the nearest competing tool, leaving a small ambiguity.

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 enumerated series list implicitly tells an agent when this tool applies (official macro/rate data), and the 'up to 6 series' batch constraint is stated. However, there is no explicit when-to-use/when-not guidance and no mention of econ_indicator, fx, or markets as alternatives for overlapping data needs.

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

All SiteCheck 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