Skip to main content
Glama

equibles

by io.github.daniel3303

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; 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.
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.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds significant behavioral context: it defines the scoring components (net buyers, shares bought as % of outstanding, net buy value), explains the data source (Forms 4/5, excluding 10b5-1) and crucially states 'Filters never renumber the universe rank' — essential for interpreting results. Goes well 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core purpose, then methodology, then usage options. No wasted words; every sentence contributes value. The structure flows logically from what to how to when.

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?

Even without an output schema, the description conveys key output components (score, factors, rank, net buyers, shares bought, buy value) and behavior (filters don't renumber rank). It also cross-references GetInsiderTransactions for raw filings. An agent can understand what to expect and how to call it correctly.

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 all parameters have individual descriptions. The tool description adds contextual usage semantics: 'pass ticker for one stock's factors and universe rank' and 'request the bottom ranking for distribution' clarify how bottom and ticker interact with filters. This adds meaning beyond the schema, though not exhaustive.

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 (rank) and resource (stocks) with a precise definition: 'peer-relative 0-100 insider-accumulation score over 90 days'. It also outlines the methodology (Form 4/5, excluding 10b5-1) and differentiates from siblings by pointing to GetInsiderTransactions for filings. Clear and unambiguous.

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?

Provides context on when to use: for ranking by insider sentiment, with options for cluster buys, liquidity, bottom ranking, or single-ticker lookup. It explicitly directs to GetInsiderTransactions for raw filings, but does not contrast with all alternative scoring tools (e.g., GetInsiderOwnership). Still, usage scenarios are well implied.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, with detailed descriptions that cross-reference related alternatives. A few near-duplicate names could cause misselection, notably SearchDocument versus SearchDocuments and GetCftcPositioning versus GetLatestCftcPositioning.

Naming Consistency5/5

Tool names consistently follow a VerbNoun camelCase pattern: Get for retrievals, Search for discovery, List/Read for document access, and Add/Close/Remove/Update/Watch/Create/Delete for portfolio mutations. Despite the large count, there is no mixing of naming conventions or unpredictable verb styles.

Tool Count1/5

108 tools is an extreme surface area, far beyond the 3-15 well-scoped range and well past the 25+ threshold. Even for a broad financial data platform, this creates a heavy selection burden and substantial context overhead for agents.

Completeness4/5

The server covers an unusually wide domain: prices, fundamentals, SEC filings, options, insider activity, 13F holdings, short interest, macro data, funds, IPOs, and full portfolio lifecycle management. Notable gaps remain, such as a basic company profile/ticker-resolution tool, dividend history, and analyst estimates, so it is not a perfect 5.

Resources