Skip to main content
Glama

Antevo Executive Brief

by ch.antevo.api

List executive notes

list_executive_notes
Read-onlyIdempotent

The archive of past Executive Briefs, newest first — each with its date, title, subtitle and hero line. Use this to see what has been covered, to find the date of a story, or to follow how a theme developed over time, then call get_executive_note for the full text of a given day.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
marketNoglobal

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.2/5.0
Behavior4/5

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

Annotations already declare this as readOnly, idempotent, and non-destructive. The description adds useful behavioral context by noting the ordering ('newest first'), the archive scope, and that only summaries are returned. This goes beyond the annotations without contradicting them.

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?

The description is two sentences with no filler. It front-loads the core definition and return content, then provides concise usage guidance and cross-referencing. 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 explains what the tool lists and how to proceed to full text, and an output schema exists so return structure is covered. However, the two optional parameters, especially 'market', are left undocumented, which is a meaningful gap for a tool intended to list archived briefs. Overall adequate but not fully complete.

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%, and the description does not explain either 'limit' or 'market'. While 'limit' may be self-explanatory, 'market' is ambiguous and lacks any guidance about acceptable values or how it affects results. The description fails to compensate for the schema's missing parameter documentation.

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 clearly states a specific action ('list') and resource ('executive notes'), characterizes the archive as 'past Executive Briefs, newest first', and enumerates the fields returned (date, title, subtitle, hero line). It also differentiates itself by pointing to get_executive_note for full text, so an agent can distinguish this tool from its sibling.

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?

The description gives explicit use cases: 'see what has been covered', 'find the date of a story', and 'follow how a theme developed over time'. It also names the alternative get_executive_note and tells the agent to call it for full text, making the routing between tools clear.

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