Skip to main content
Glama

Signal Nodus SEC Filings

by ai.signalnodus

Which institutions hold a stock

who_holds
Read-only

Every 13F manager whose latest information table names the company: manager, CIK, filing date, accession number, plus the total count of reporting managers. The inverse of institutional_holdings; chain them to walk from a ticker to full parsed portfolios. Costs $0.05 per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoManagers to return. Default 25.
companyYesTicker symbol (e.g. AAPL) or SEC CIK number (e.g. 320193).

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. Description adds meaningful context: the $0.05/call cost, the 'latest information table' freshness nuance, and the total count of managers. This goes beyond what annotations provide.

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 deliver all essential information: output contents, relationship to sibling, and cost. No fluff, perfectly front-loaded.

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 low-complexity tool with two well-documented parameters and no output schema, the description covers purpose, output fields, pricing, and usage context. Could mention pagination or sorting but it's not essential.

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 clear parameter explanations (ticker/CIK, limit default). The text doesn't add parameter-level detail, but none is needed; baseline 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?

Description clearly states it returns 13F managers and their fields (manager, CIK, filing date, accession number) for a company. The phrase 'The inverse of institutional_holdings' actively distinguishes it from a sibling tool, leaving no ambiguity about its function.

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?

Explicitly names the sibling 'institutional_holdings' as its inverse and suggests chaining them to walk from ticker to portfolios. This gives concrete when-to-use guidance and an alternative, satisfying the top criterion.

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

All Signal Nodus SEC Filings 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

A3.5/5.0
Disambiguation3/5

Most tools have clearly written descriptions, but several pairs overlap semantically: token_price/token_report, latest_filings/recent_filings, and institutional_holdings/who_holds/activist_stakes all require careful reading to pick the right one. The overlap is not severe enough for a 2, but it is still more than the occasional confusion.

Naming Consistency3/5

Names are consistently snake_case and mostly descriptive, but the set does not follow one naming convention. It mixes noun phrases (crop_data, token_report, insider_trades) with verb phrases (lookup_company, compare_filings, verify_financial_claim), and pairs like latest_filings/recent_filings create avoidable confusion.

Tool Count2/5

31 tools is too many for what is nominally an SEC Filings server, and the scope sprawls into unrelated domains such as EVM gas, tokens, prediction markets, crop data, and x402 auditing. The count does not feel earned by a coherent workflow; it feels like an uncurated bundle of endpoints.

Completeness3/5

The SEC filing workflow is reasonably covered: company lookup, search, latest/recent filings, section extraction, 8-K events, comparisons, ownership filings, and XBRL financial checks are all present. However, there is no full-filing retrieval endpoint, no deep company financial history beyond a single concept, and many non-SEC subdomains are only one-off data points, so the overall surface is still incomplete.

Resources