Skip to main content
Glama

Basis

by com.basischarts
OverviewDiscussionsAdmin

calendar_history

Read-onlyIdempotent

Past calendar dates: FOMC rate decisions, US CPI and non-farm payroll releases from the Fed's and BLS's published calendars (February 2025 on), plus reconstructed conventions (options expiry, CME settlement). Dates only: NOT actual, forecast or previous economic values. No historical funding or halving feed. Use calendar_upcoming for future events.

Input Schema

NameRequiredDescriptionDefault
toNoA date or timestamp, e.g. 2026-09-01 or 2026-09-01T00:00:00Z. UTC unless it says otherwise.
fromYesA date or timestamp, e.g. 2026-09-01 or 2026-09-01T00:00:00Z. UTC unless it says otherwise.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / from / description
      Previous value: -"ISO 8601 timestamp with timezone, e.g. 2026-09-01T00:00:00Z."New value: +"A date or timestamp, e.g. 2026-09-01 or 2026-09-01T00:00:00Z. UTC unless it says otherwise."
    • changedInput schema / properties / to / description
      Previous value: -"ISO 8601 timestamp with timezone, e.g. 2026-09-01T00:00:00Z."New value: +"A date or timestamp, e.g. 2026-09-01 or 2026-09-01T00:00:00Z. UTC unless it says otherwise."
    • changedInput schema / required
      Previous value: -[
-  "from",
-  "to"
-]New value: +[
+  "from"
+]
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the bar is lower. The description adds real content-level behavior: the data provenance (published Fed/BLS calendars vs reconstructed conventions) and the coverage start date, which the annotations cannot convey.

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?

Dense and front-loaded: scope, then contents, then exclusions, then the sibling pointer. Every clause carries information, though the telegraphic 'Dates only: NOT...' style and the trailing routing sentence make it slightly less scannable than it could be.

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?

With no output schema, the description correctly discloses the return shape ('dates only, not actual/forecast/previous values') and the temporal coverage boundary. Minor gap: no pagination or result-size behavior for wide date ranges.

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 both from/to parameters are documented in the schema with date/timestamp format and UTC convention. The description adds nothing about parameter syntax or defaults, so baseline 3 is appropriate.

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 (past calendar dates) with enumerated contents (FOMC rate decisions, US CPI, non-farm payrolls, options expiry, CME settlement) and an explicit coverage window (February 2025 on). An agent can distinguish this from calendar_upcoming and news_history without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the sibling alternative and the condition selecting it: 'Use calendar_upcoming for future events.' It also states exclusions (no actual/forecast/previous values, no historical funding or halving feed), which prevents mis-selection for value or funding queries.

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

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