Skip to main content
Glama

Antevo Executive Brief

by ch.antevo.api

Get macro series

get_macro_series
Read-onlyIdempotent

One macro series by ticker, newest first, with the date of its most recent observation stated on the response. These are QUARTERLY levels and they lag — the newest point is a quarter end, never today. Use search_macro_indicators to find the ticker. Optional since/until (YYYY-MM-DD) narrow the window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
sinceNo
untilNo
tickerYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/destructive annotations, it discloses that results are ordered newest-first, that the response explicitly includes the date of the most recent observation, and that the underlying frequency is quarterly with a lag. These are meaningful behavioral traits that shape expectations. It does not contradict the annotations.

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 tight sentences, each carrying substantive information: core behavior, data lag caveat, sibling pointer and optional date window. No filler or restatement of the title.

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?

The tool is well covered given the presence of an output schema and annotations: purpose, ordering, lag, date window, and sibling routing are all present. The only completeness gap is the undocumented limit parameter, but the default value in the schema partially mitigates the risk.

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?

With 0% schema description coverage, the description must explain parameters. It covers since/until by giving the YYYY-MM-DD format and saying they narrow the window, and implies ticker is the key selector. However, the limit parameter is never explained, leaving its meaning (likely max observations) to inference.

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: retrieve one macro series by ticker, sorted newest first, and includes the date of the most recent observation. It differentiates from search_macro_indicators, which is for finding a ticker, and from the other market/report siblings.

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?

It explicitly directs the agent to use search_macro_indicators to discover the ticker, providing a clear alternative for a different need. It also warns that data are quarterly and lagged (newest point is a quarter end, never today), which helps the agent judge when this tool is appropriate.

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

All Antevo Executive Brief toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

Most tools map clearly to distinct resources: get_* for retrieval, list_* for enumeration, search_* for lookup, track_* for time series. Some overlap exists between get_executive_brief, get_executive_note, and get_executive_desk, and between get_indices and get_market_snapshot, but descriptions clarify the intended use. Overall an agent can usually tell which tool to pick with little ambiguity.

Naming Consistency5/5

Tool names follow a highly consistent snake_case verb_noun pattern: get_, list_, search_, and track_ prefixes clearly indicate the operation. Resource nouns like executive_brief, risk_radar, world_events, and macro_series are descriptive and predictable. There are no mixed conventions or vague verbs.

Tool Count4/5

Fifteen tools is on the higher end but remains within a reasonable range for a server covering briefs, notes, coverage areas, macro data, market snapshots, and risk tracking. Each tool has a plausible purpose, though a few could arguably be consolidated, such as the separate executive brief/note/desk retrieval tools. The count does not feel bloated or excessive for the stated scope.

Completeness4/5

The tool surface covers the core lifecycle of the domain: listing and retrieving briefs, coverage, macro series, indices, risk radars, and world events, plus search for macro indicators. Minor gaps exist, such as no way to search editorial briefs or coverage notes by keyword, and no direct retrieveal of catalysts beyond a forward horizon. These are workable gaps and do not prevent most agent workflows.

Resources