Skip to main content
Glama

Equibles

by io.github.daniel3303
OverviewDiscussionsAdmin

Insider Sentiment Scores

GetInsiderSentimentScores
Read-only

Rank stocks by a peer-relative 0-100 insider-accumulation score over 90 days: net buyers, net shares bought as a percent of shares outstanding, and net buy value. It uses qualifying open-market Forms 4/5 purchases and sales by officers and directors (a holder that is only a 10% owner is excluded); Form 3 establishes initial ownership, and disclosed Rule 10b5-1 trades are excluded. Filter for cluster buys or liquidity, request the bottom ranking for distribution, or pass ticker for one stock's factors and universe rank. Filters never renumber the universe rank. Use GetInsiderTransactions for the filings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bottomNoReturn the LOWEST-scored stocks instead — the heaviest peer-relative net insider selling — lowest score first.
offsetNoNumber of matching ranked stocks to skip before returning rows (default: 0; ignored for a single-ticker lookup).
tickerNoOptional stock ticker (e.g. NVDA): returns that one stock's score, factor breakdown, and rank within the scored universe instead of the leaderboard. The other filters do not apply to a single-ticker lookup.
maxResultsNoMaximum number of stocks to return (default: 25, highest score first; clamped to 1-200).
minMarketCapNoMinimum market capitalization in US dollars (e.g. 300000000 = $300M; default 0 = no floor). Stocks with an unknown market cap are excluded when set.
minSharePriceNoMinimum share price in US dollars (e.g. 5 = $5; default 0 = no floor). Stocks with an unknown price are excluded when set.
clusterBuysOnlyNoReturn only stocks flagged as cluster buys (three or more distinct insiders buying in the window).
minDollarVolumeNoMinimum trailing 3-month average daily dollar volume in US dollars (e.g. 5000000 = $5M/day; default 0 = no floor). Stocks with unknown volume are excluded when set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Number of matching ranked stocks to skip before returning rows (default: 0; ignored for a single-ticker lookup).",
+  "type": "integer"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly, non-destructive, and closed-world behavior, but the description adds important methodology: the score components, the 90-day window, the use of qualifying open-market Forms 4/5, the exclusion of mere 10% owners and Rule 10b5-1 trades, and the fact that filters never renumber the universe rank. These are substantive behavioral details beyond annotations.

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?

The description is four sentences and front-loads the scoring concept, then methodology, then usage. It is dense but every sentence contributes relevant information, with no obvious filler.

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?

With no output schema, the description still explains what a caller gets (leaderboard ranking, single-ticker factor breakdown and universe rank) and how filters affect results. Combined with full schema coverage and annotations covering safety, the definition is complete enough for correct invocation.

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 each parameter is already well documented. The description adds little per-parameter meaning beyond reinforcing filter behavior and noting that filters do not renumber ranks; the baseline of 3 is appropriate when the schema carries the parameter definitions.

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 states a specific verb (Rank) and resource (stocks by a peer-relative 0-100 insider-accumulation score over 90 days), and it names the sibling GetInsiderTransactions for the underlying filings. An agent can distinguish this from other insider tools without opening the 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 describes the three main invocation modes (filter for cluster buys/liquidity, request bottom ranking for distribution, pass ticker for a single stock's factors and rank) and routes the agent to GetInsiderTransactions for raw filings. The when-to-use and alternative are both clear.

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

All Equibles toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources