Skip to main content
Glama
Heliyos MCP server

Heliyos MCP server

Official
by heliyos-ai

Get the watchlist

heliyos_watchlist_get
Read-onlyIdempotent

Lists companies on the watchlist with IDs, names, key fields, and optional watchlist statistics; use it to review monitored accounts and paginate results.

Instructions

Lists the companies on the watchlist (the accounts the workers monitor with Scouts and keep enriched), most recently created records first (not by watch date), with their ids, names and key fields. "detailed" also returns watchlist statistics on the first page: tasks done, deals, meetings and actions across watched companies. Use heliyos_companies_watch / _unwatch to change it. Returns structuredContent {companies:[{id, name, fields}], statistics?, next_cursor}.

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

Input Schema

NameRequiredDescriptionDefault
limitNoCompanies per page, 1 to 100. Default 20.
cursorNonext_cursor from the previous page, with the same limit. Omit for the first page.
response_formatNo"concise" (default) returns companies with key fields; "detailed" returns every field plus watchlist statistics.concise

Output Schema

NameRequiredDescriptionDefault
companiesYes
statisticsNo
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds non-obvious behavior: the sort key is record creation rather than watch date, and the detailed statistics block appears only on the first page. That first-page quirk is exactly the kind of thing an agent would otherwise mis-infer from a paginated call.

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?

Front-loaded with the resource and ordering, then the mode caveat, then the sibling pointer — a sensible priority order with no filler sentences. The closing structuredContent enumeration is somewhat redundant given an output schema exists, which keeps it from a 5.

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

Completeness5/5

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

For a read-only, paginated list with only three optional parameters, everything an agent needs to call it correctly is present: pagination contract, sort semantics, mode difference, and where to go to modify the list. Return values are already covered by the output schema, so the brief shape note is supplementary rather than a gap.

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 100%, so the baseline is 3, but the description adds meaning beyond the schema by clarifying that statistics accompany "the first page" only, which affects how cursor and limit interact with response_format. It doesn't expand on limit bounds or cursor reuse, leaving those to the schema.

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?

States a specific verb and resource ("Lists the companies on the watchlist") and defines the concept inline as "the accounts the workers monitor with Scouts and keep enriched." It also pins down ordering ("most recently created records first (not by watch date)"), which no sibling tool covers, so an agent can distinguish it from records_list or companies_watch 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 Guidelines4/5

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

Explicitly routes mutation intent to heliyos_companies_watch / _unwatch, which is the main confusion risk for a fetch-only tool. It does not contrast itself against adjacent read tools like heliyos_companies_scouts_list or heliyos_records_list, so the when-not guidance is partial rather than complete.

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