Skip to main content
Glama

SN Data by Shikshan Nivesh

Planned insider sales (Form 144)

get_planned_sales
Read-onlyIdempotent

Form 144 notices of planned sales, newest first: who, relationship, shares, value, planned date and the filing.

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": {
      "ticker": "<ticker>"
    },
    "name": "get_planned_sales"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOnly rows on or before this date (year-month-day).
fromNoOnly rows on or after this date (year-month-day).
limitNoMost rows to return, newest first. Default 25.
tickerYesThe company's ticker, like AAPL. BRK.B and BRK-B both work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds useful context beyond that — newest-first ordering and the specific fields in the response — but says nothing about volume, coverage of issuers, or latency for a potentially large filing feed.

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 front-loaded sentence: the resource and ordering come first, then the returned fields. No filler or repeated metadata, though the colon-delimited field list is terse enough to be slightly opaque.

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 simple read-only filtered list with full schema coverage, complete annotations, and no output schema, the definition covers what is needed — and the field enumeration substitutes for a return-value description. The only real gap is the absence of routing guidance against the closely related insider-trades tool.

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%, with formats, defaults, and limits all documented in the schema itself, so the baseline is 3. The description only reinforces that results come newest first, matching the limit parameter's documented ordering, and adds no date-range or ticker semantics beyond the schema.

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 verb+resource combination: Form 144 notices of planned sales, and enumerates the fields returned (who, relationship, shares, value, planned date, filing). This clearly separates it from an executed-trades tool in concept, though it never names a sibling such as get_insider_trades to make the distinction explicit.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no mention of alternatives among the sibling tools. The word 'planned' implicitly contrasts with actual insider trades, but the agent must infer that this is the pre-transaction notice feed rather than the executed-transactions feed.

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