Skip to main content
Glama

Market Intelligence API (core)

Fed rate odds

macro.fed_odds
Read-onlyIdempotent

Fed rate decision odds ($0.10): probability of a cut, no change or a hike at the next FOMC and other central-bank decisions, from Hyperliquid prediction markets, with 24h change, volume and the decision date.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "macro.fed_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld behavior, so the safety profile is covered. Beyond that, the description discloses a per-call cost ($0.10), the external data source, and the shape of the payload (24h change, volume, decision date), which is genuine behavioral context an agent needs before spending.

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?

A single sentence that front-loads the resource name and cost, then qualifies source and returned fields in a compact parenthetical. No filler or repetition; every clause carries information an agent would otherwise have to guess.

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?

For a zero-parameter, read-only lookup with no output schema, the description supplies everything needed: what is returned, from where, at what price, and over what horizon. Nothing material is missing for correct invocation.

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?

The tool takes no parameters, so there is nothing to disambiguate and the baseline is 4. The description correctly implies a fixed, argument-free query, consistent with the empty input 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?

States a specific resource (Fed rate decision odds) with the exact quantities returned (probability of a cut, no change, or a hike at the next FOMC) and broadens scope to other central-bank decisions. The source (Hyperliquid prediction markets) further pins down what the data actually is, so an agent can distinguish it from sibling market/prediction tools without opening the schema.

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?

Usage is implied by the content — an agent should call this when it needs rate-decision probabilities — but there is no explicit when-to-use or when-not-to-use guidance, and no named alternative such as markets.prediction for other prediction-market queries. Adequate but inferential.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources