Skip to main content
Glama

Arkanum Data: SEC insider trades

Watchlist warnings

watchlist_warnings
Read-only

New red flags for your watchlist from SEC filings, kept 30 days: serious 8-Ks, repeated leadership changes, finances turning to losses, heavy insider selling, late insider filings. Hobby and Pro.

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

Input Schema

NameRequiredDescriptionDefault
sinceNoOnly warnings found after this ISO time

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 readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: results are bounded to a 30-day retention window, and access is gated to the Hobby and Pro tiers. It does not disclose ordering, volume of results, or what an empty response means, but against annotation coverage this is solid.

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?

A single tight sentence, front-loaded with purpose and retention before the category list, with zero filler. The trailing 'Hobby and Pro.' fragment is terse to the point of ambiguity about what it constrains, but the overall density is appropriate for a simple 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 one-parameter, read-only list tool with no output schema, the description covers source, retention, warning taxonomy, and plan eligibility — enough to call it correctly and interpret results. The remaining gap is the unstated watchlist prerequisite and any guidance on incremental polling via 'since'.

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?

There is a single optional 'since' parameter with 100% schema description coverage, so the schema already defines it as an ISO time filter. The description references neither the parameter nor an incremental-polling pattern (which would be the natural use of 'since' given the 30-day retention). Baseline 3 applies when the schema carries the parameter documentation.

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 outcome: new red flags for the user's watchlist derived from SEC filings, with the concrete warning categories enumerated (8-Ks, leadership changes, losses, insider selling, late filings). The 'from SEC filings' source and 30-day retention make the scope unambiguous. It does not, however, distinguish itself from the sibling market_warnings, so an agent must infer the watchlist-vs-market distinction from the name alone.

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: 'for your watchlist' signals a prerequisite that a watchlist exists (set_watchlist/get_watchlist), and 'Hobby and Pro' signals a plan-tier gate. There is no explicit when-to-use versus when-to-use-alternatives guidance, and no statement of what happens if the user has no watchlist configured or is on a different plan.

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.

Resources