Skip to main content
Glama

Arkanum Data: SEC insider trades

Set watchlist

set_watchlist

Replaces your watchlist (up to 50 tickers on Hobby, 1,000 on Pro). New red flags for these stocks appear in watchlist_warnings. Hobby and Pro.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tickers": "<tickers>"
    },
    "name": "set_watchlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickersYes
morning_emailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false; the description supplies genuinely additive behavior: the operation is a wholesale replacement, the ticker cap is tier-dependent (50 vs 1,000), and results surface later through watchlist_warnings. It does not disclose what happens on exceeding the cap, invalid tickers, or whether the prior list is recoverable.

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?

Three short sentences, front-loaded with the core action and its cap; nothing is padded. The trailing 'Hobby and Pro.' fragment restates the plan gating already implied by the tier limits, so it is minor dead weight.

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

Completeness3/5

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

For a two-parameter mutation with no output schema, the description covers replacement semantics, limits, and downstream effects well. It is still incomplete on the undocumented morning_email parameter and on failure behavior at the ticker limit, which an agent would need before calling.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden for both parameters. It gives a size constraint for 'tickers' but never states the expected format (symbols vs. IDs), and 'morning_email' is entirely unmentioned, leaving the boolean's effect unguessable.

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?

'Replaces your watchlist' states a specific verb and resource, and 'Replaces' correctly signals full-overwrite semantics rather than an append, which distinguishes it from get_watchlist. It does not explicitly name a sibling to contrast with, so it stops short of a 5.

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?

Plan gating ('Hobby and Pro') is stated and the downstream consumer (watchlist_warnings) is pointed at, giving implied usage context. However, nothing says when to use this instead of get_watchlist or whether the list must exist first; the when-to-use is inferred from the verb rather than stated.

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