Skip to main content
Glama
bykarantelicom

bykaranteli-mcp

by bykarantelicom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Macro liquidity: Fed funds, 10y, balance sheet, RRP, stablecoin supply

get_macro_liquidity
Read-only

Retrieve daily macro liquidity series—Fed balance sheet, reverse repo, rates, and stablecoin supply—to assess crypto conditions and return latest values or a custom date window.

Instructions

Call this when the user asks about macro liquidity, the Fed balance sheet, reverse repo, rates or stablecoin supply in relation to crypto. Returns the recorded daily series and latest values. Without days, each series holds its newest 7 points; pass days for the daily series, and series for one key over a long window.

Input Schema

NameRequiredDescriptionDefault
daysNoWindow in days, 30-4000; the route clamps to that range. Omit for the newest 7 points of each series.
seriesNoOptional. One series key from the answer's series field, e.g. fred_walcl_busd.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed2 schema fields changedv0.36.0
    • changedInput schema / properties / days / description
      Previous value: -"Window in days, 30-4000 (default 365); the route clamps to that range."New value: +"Window in days, 30-4000; the route clamps to that range. Omit for the newest 7 points of each series."
    • addedInput schema / properties / series
      Added value: +{
+  "description": "Optional. One series key from the answer's series field, e.g. fred_walcl_busd.",
+  "pattern": "^[a-z0-9_]{2,60}$",
+  "type": "string"
+}
  3. Changed3 schema fields changedv0.31.0
    • changedInput schema / properties / days / description
      Previous value: -"Window in days, 1-730 (default 365)."New value: +"Window in days, 30-4000 (default 365); the route clamps to that range."
    • changedInput schema / properties / days / maximum
      Previous value: -730New value: +4000
    • changedInput schema / properties / days / minimum
      Previous value: -1New value: +30
  4. Addedv0.9.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real behavioral detail beyond that: the return consists of recorded daily series plus latest values, and omitting days yields only the newest 7 points per series, which is a meaningful default an agent must know. It does not discuss data freshness, source, or gaps.

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?

Three sentences, front-loaded with the trigger, then return shape, then parameter guidance. No filler. Slightly dense phrasing ("pass days for the daily series, and series for one key over a long window") but every clause carries information.

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 two-parameter, no-required-argument read tool with no output schema, the description covers trigger, return shape, and default window behavior. The only gap is that it does not enumerate or point to how an agent discovers valid series keys beyond the schema's note about the answer's series field.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds the interaction between the two parameters: days controls the daily series, series narrows to one key over a long window. That combination logic is not obvious from either schema field alone, so it earns above baseline.

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?

States a specific resource (macro liquidity: Fed balance sheet, reverse repo, rates, stablecoin supply) and what it returns (recorded daily series and latest values). An agent can tell it is a macro-series reader rather than an on-chain or venue tool. It stops short of naming a sibling it could be confused with, such as get_series or get_tradfi_board.

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?

"Call this when the user asks about macro liquidity, the Fed balance sheet, reverse repo, rates or stablecoin supply in relation to crypto" gives an explicit trigger condition. It also tells the agent which parameter form to pick: omit days for short default windows, supply days for the daily series, supply series for one key over a long window. No exclusion of alternatives is stated.

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