Skip to main content
Glama
Heliyos MCP server

Heliyos MCP server

Official
by heliyos-ai

List scouts

heliyos_scouts_list
Read-onlyIdempotent

Lists built-in and custom scouts that monitor watched companies or the web for events such as funding, hiring, or leadership changes, showing each scout's status, cadence, and signal counts.

Instructions

Lists the workspace's scouts: the built-in (default) and custom monitors that look for events such as funding, hiring or leadership changes on watched companies or across the web. Shows each scout's id, whether it is active, its cadence, and how many signals it found (new of total). Returns every scout (there are only a few, so there is no paging). Use heliyos_scouts_get for one scout's query and recent signals, heliyos_signals_list for what scouts found. Returns structuredContent {scouts:[{id, name, type, is_active, ...}]}.

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": "heliyos_scouts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOnly built-in (default) or only custom scouts.
apply_toNoOnly scouts with this scope.
is_activeNoOnly active (true) or only paused and unconfirmed (false) scouts.
response_formatNo"concise" (default) returns one row per scout; "detailed" returns category, scope, effort and preview state too.concise

Output Schema

NameRequiredDescriptionDefault
scoutsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds value beyond that by noting the result set is small and unpaged and by describing the signal-count semantics (new of total). It does not discuss filter combination behavior (e.g., whether type, apply_to and is_active AND together), which is the main remaining behavioral gap.

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

Conciseness4/5

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

It is a single dense paragraph that front-loads the definition of a scout before the sibling routing and the return summary. Almost every sentence carries information, though the explicit structuredContent field listing partially duplicates the existing output schema.

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?

This is a simple, zero-required-parameter read tool with annotations and an output schema, and the description covers scope, non-paging behavior, sibling alternatives and the headline return fields. Only the interaction between the optional filters is left implicit, a minor gap for this complexity level.

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?

Schema description coverage is 100% and three of four parameters are enums with documented values, so the schema carries the parameter semantics. The description does not restate or extend filter meaning beyond noting which fields are surfaced per scout. Baseline 3 is appropriate given the schema does the heavy lifting.

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 uses a specific verb and resource ("Lists the workspace's scouts") and immediately defines what a scout is: built-in (default) and custom monitors watching companies or the web for funding, hiring or leadership changes. It also states the per-item fields returned (id, active state, cadence, signal counts), so an agent can distinguish it from siblings like heliyos_scouts_get or heliyos_signals_list without opening a schema.

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 routes the agent: use heliyos_scouts_get for one scout's query and recent signals, and heliyos_signals_list for what scouts found, leaving this tool for enumerating scouts. It also removes a common ambiguity by stating there is no paging because the set is small, so the agent knows not to look for offset/limit parameters.

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

Deploy Server

Other Tools