Skip to main content
Glama

Strategy Radar

Strategy Radar set-up

get_strategy_radar_setup
Read-onlyIdempotent

Set up Strategy Radar for a company: everything a company's own assistant needs to match Antevo's daily business board of risks and opportunities to that company's strategy. Returns the five setup questions (about three minutes, no figures) and the fuller profile, the exposure-tag vocabulary, the matching method, the text of a weekday morning task, the page layout for drawing the radar, and the two disclosure lines. Takes no input: the company's answers stay with its assistant and never reach Antevo.

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_strategy_radar_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real context beyond them: no input is taken, the company's answers stay with its assistant and never reach Antevo, and the setup is framed as roughly three minutes with no figures required. It does not mention rate limits or failure modes, which is a minor gap.

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 and privacy note are front-loaded and earn their place, but the sentence then enumerates the full return payload (setup questions, profile, exposure-tag vocabulary, matching method, task text, page layout, disclosure lines). Since an output schema exists, that inventory is largely redundant and inflates the description considerably.

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?

With an output schema present, the return values need not be described, and the description is still complete enough for an agent to call this correctly: intent, zero-input contract, and the privacy boundary are all covered. What is missing is only the relative placement among siblings, which is a small gap for a simple no-argument tool.

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?

The tool has zero parameters, which establishes a baseline of 4. The description reinforces this explicitly with 'Takes no input', leaving no ambiguity about whether a company identifier or date range is expected.

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?

The description names a specific resource ('Strategy Radar') and states the outcome: everything a company's assistant needs to match Antevo's daily business board to that company's strategy. The verb 'Set up' is slightly misleading for a no-input read-only retrieval, but the body immediately clarifies it returns a setup kit rather than mutating anything. It is clearly distinct from data siblings such as get_risk_radar or get_business_board.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent can infer this is the onboarding/configuration call for a company assistant, and that it takes no inputs. There is no explicit when-to-use/when-not guidance and no named alternative (e.g. when to call get_risk_radar instead for actual radar data), so the agent must infer the routing.

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.