Skip to main content
Glama

Strategy Radar

Business board

get_business_board
Read-onlyIdempotent

What changed for a company's strategy today: Antevo's business board for the day, the board behind Strategy Radar. Risks and opportunities for companies from trade, regulation, supply, shipping, energy, demand, currencies, funding, labour, technology, cyber, geopolitics and climate. Each entry carries its theme, exposure tags, impact, likelihood and trend in words, why it matters with a date, what to watch, the event that would make a response right, and two or three possible responses with their reasons. Pass as_of (YYYY-MM-DD) for a past board within the last 400 days. Takes no company details; matching to a company happens in the company's own assistant.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_business_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the 400-day lookback bound and the no-company-filtering behavior, which is genuine value, but it does not address pagination, entry counts, or freshness beyond 'for the day.'

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the second sentence is a dense catalogue of themes and entry fields that is partly duplicated by the output schema. It is informative but heavier than needed for a one-parameter read tool.

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?

For a parameterless read with an output schema, an agent needs to know what it returns, when it is applicable, and how to request a past board — all covered. The enumeration of entry fields is redundant given the output schema, but nothing essential to invoking it correctly is missing.

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

Parameters4/5

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

Schema coverage is 0% for the single as_of parameter, so the description must carry the meaning, and it does: date format YYYY-MM-DD, the default of today's board, and the 400-day limit. That is close to full compensation, with only timezone/date-boundary semantics left unstated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: 'Antevo's business board for the day, the board behind Strategy Radar,' and enumerates the risk/opportunity themes it covers. An agent can tell it is the daily strategic board rather than a series or event feed, though it never explicitly contrasts itself with siblings like get_risk_radar or get_executive_brief.

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?

'Pass as_of (YYYY-MM-DD) for a past board within the last 400 days' plus 'Takes no company details; matching to a company happens in the company's own assistant' are effective when/when-not constraints that prevent a wrong invocation. It stops short of naming an alternative tool for company-level or historical-beyond-400-days needs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.