Skip to main content
Glama

fomc-calendar

FOMC calendar. No input: the 2026 and 2027 FOMC schedule (plus the announced January 2028 meeting) with the next and previous meeting, day counts to and from the decision day, the between-meetings to day-after-decision state ladder, and the strategy-only October 2027 flag, answered fresh on every call. Price: $0.005 per call, paid in USDC on Base mainnet over x402; an unpaid call answers HTTP 402 with the exact machine-readable payment terms.

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": "fomc-calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the pricing model ($0.005 per call, USDC on Base mainnet via x402), the failure mode (unpaid call returns HTTP 402 with machine-readable payment terms), and the freshness guarantee. It does not describe response shape or error behavior beyond payment, which keeps it from a 5.

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?

It is front-loaded with the resource and the no-input fact, then the return contents, then payment terms — a sensible order. The single dense sentence packs in jargon like 'between-meetings to day-after-decision state ladder' and 'strategy-only October 2027 flag' without explanation, which costs some readability.

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?

There is no output schema, so the description must describe return values, and it does so by enumerating the fields returned. Payment and freshness are covered; only the exact response structure and error cases beyond HTTP 402 are left implicit, which is a minor gap for a zero-parameter read tool.

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 zero parameters, so the baseline is 4, and the description reinforces this by explicitly stating 'No input', removing any ambiguity about whether arguments are expected.

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?

The description names a specific resource (FOMC calendar) and enumerates exactly what it returns: the 2026/2027 schedule plus the announced January 2028 meeting, next/previous meeting, day counts to and from the decision day, the between-meetings state ladder, and the October 2027 flag. An agent can tell this apart from siblings like next-federal-holiday or market-open without opening a 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?

It states 'No input' and that results are answered fresh on every call, which implies when the tool is appropriate, but it gives no explicit when-to-use/when-not guidance and names no alternative for related date or market-calendar needs. Usage is implied rather than directed.

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