Antevo Executive Brief

Get risk radar

get_risk_radar

Read-onlyIdempotent

The risk radar — what the Antevo Executive Brief judges could go wrong from here, each with its trend, impact, probability and why it matters, plus the regime it sits in and the indicators that would confirm or kill it. Pass as_of (YYYY-MM-DD) for the radar as it stood on a past date. For how risks have DEVELOPED over weeks, use track_risk_evolution.

Input Schema

TableJSON Schema

Name	Required	Default
`as_of`	No
`scope`	No	retail
`market`	No	global

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

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

First observedSep 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavior beyond annotations: it returns a point-in-time snapshot and supports historical as-of dates, which is not visible in 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?

Two dense sentences with no filler. The first sentence front-loads the core value and output contents; the second handles historical usage and sibling differentiation. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description richly covers outputs (and an output schema exists) and explains as_of, but it omits scope and market semantics that an agent would need to parameterize calls for different radar views. It is adequate for a basic call with defaults but not fully complete for the tool's intended variations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It documents as_of format and meaning, but says nothing about scope or market — two of the three parameters — leaving their semantics to guesswork despite defaults 'retail' and 'global'. This is a substantial gap.

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 identifies a specific deliverable — the risk radar as judged by the Antevo Executive Brief — and enumerates its contents (trend, impact, probability, why it matters, regime, indicators). It also distinguishes from track_risk_evolution by positioning that sibling as the tool for how risks have developed over weeks.

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 states when to use this tool (to see current or as-of risk radar), how to pass a historical date ('Pass as_of (YYYY-MM-DD)'), and explicitly routes trend-over-time use to track_risk_evolution. This gives clear contextual choice guidance against the main sibling.

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 tools Inspect

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

Need Help?