Skip to main content
Glama
signal8ai

Signal8 MCP Server

Official

Get Top Institutions by AUM

get_institution_top_aum
Read-only

Discover top institutional holders ranked by assets under management across all companies. Optionally filter by minimum AUM to identify smart money flows.

Instructions

Discover top institutional holders across the entire company universe ranked by assets under management (AUM). Unlike get_ownership which shows institutions for a single company, this tool searches across all companies to find the largest institutional players. Optionally set a minimum AUM. Useful for identifying smart money flows and major institutional positioning trends.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum results to return (default: 25, max: 100)
minAumNoMinimum AUM in USD to filter institutions (e.g., 1000000000 for $1B+)
offsetNoOffset for pagination (default: 0)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so no additional safety disclosure needed. Description adds behavioral context: searches across all companies, ranks by AUM, optionally filters by minimum AUM. Does not mention pagination or return format, but output schema exists (not shown) to cover that.

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?

Two sentences, well-structured. The first sentence fronts the core purpose and scope. The second sentence adds differentiation and optional feature. Very little redundancy, though could be slightly more concise.

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?

Given simple tool with 3 optional parameters, readOnlyHint annotations, and output schema present, the description adequately covers key aspects (purpose, scope, differentiation, optional filter). Satisfies completeness for this level of complexity.

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% (all three parameters documented). The description adds a brief mention of minimum AUM but no additional semantic value beyond what the schema already provides. Baseline score of 3 is appropriate.

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?

Clearly states 'Discover top institutional holders across the entire company universe ranked by assets under management (AUM)' with a specific verb and resource. Explicitly distinguishes from sibling tool get_ownership by noting the scope difference (across all companies vs. single company).

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 explicit context for when to use this tool compared to get_ownership (single company vs. all companies). Mentions optional parameter (minimum AUM) and practical use case ('identifying smart money flows'). Lacks explicit when-not-to-use statements but sufficiently guides selection.

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

Deploy Server

Other Tools