MacroTape market brief

MacroTape brief for a date

get_brief_by_date

Read-onlyIdempotent

A past MacroTape brief by date (YYYY-MM-DD, U.S. weekdays) and optional edition (am|pm; omit for the newest edition that day). List available dates with the open /api/index.json. Needs an API key: send 'Authorization: Bearer ' or 'X-API-Key: ' on the HTTP connection. Counts against the key's daily limit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>"
    },
    "name": "get_brief_by_date"
  }
}

Input Schema

Name	Required	Description	Default
`date`	Yes	Brief date, YYYY-MM-DD.
`format`	No	text = one compact line; json = full structured brief.	json
`edition`	No	am = overnight edition (~7 AM ET); pm = midday edition (~1 PM ET). Omit for the newest edition that day.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 10, 2026

changedInput schema / properties / edition / description

Previous value: -"Optional edition."New value: +"am = overnight edition (~7 AM ET); pm = midday edition (~1 PM ET). Omit for the newest edition that day."

addedInput schema / properties / format / description

Added value: +"text = one compact line; json = full structured brief."

First observedOct 20, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, closed-world behavior, and the description adds the things annotations cannot: authentication is required with the exact header forms, calls count against a daily key limit, and the past-only scope with U.S. weekday restriction. Those are precisely the operational constraints an agent needs before calling.

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?

Three sentences, each carrying distinct information: resource identity, date-listing alternative, and auth/rate-limit constraints. Nothing is repeated from the schema verbatim beyond the necessary date format reminder, and the core identity is front-loaded.

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 single-read tool with full schema coverage and annotations covering the safety profile, the description supplies the remaining essentials: auth mechanism, rate-limit accounting, weekday restriction, and a discovery endpoint for valid dates. No output schema exists, yet the format enum ('one compact line' vs 'full structured brief') already signals return shape adequately.

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%, so the schema already documents date, format, and edition with enums and defaults. The description reinforces the date pattern and the edition omission rule, but adds no format syntax or edge-case handling beyond what the schema states. Baseline 3 applies when the schema does the heavy lifting.

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 states a specific verb and resource ('A past MacroTape brief by date') and immediately scopes it with the date format, weekday restriction, and edition selector. It is clearly distinguishable from get_latest_brief and get_history by the explicit date parameterization.

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?

It says when to omit edition ('omit for the newest edition that day') and points to /api/index.json for listing available dates, which is real routing guidance. It does not explicitly contrast with get_latest_brief or get_history, so an agent must infer that choice from the names.

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

All MacroTape market brief tools Inspect

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

Need Help?