Market and Regulatory Data Feeds — Zinin M2M Hub

13F Portfolio Tracker

thirteen-f-tracker

Read-only

Track institutional managers (hedge funds, family offices) by SEC CIK or name and get their recent 13F-HR quarterly filings — form, filing date, accession number and an EDGAR link. Official SEC data, free, no API key or login. — $0.01/call, x402 (USDC on base).

Input Schema

TableJSON Schema

Name	Required	Description
`managers`	Yes	Institutional managers to watch — each entry is either a 10-digit SEC CIK (e.g. `0001067983` for Berkshire Hathaway, used as-is) or a manager name resolved against EDGAR's filer index (e.g. `Bridgewater Associates`). A name that matches several filers returns the shortlist with similarity scores instead of picking one, so use the CIK or the full filer name for anything generic like `Capital Management`.
`sinceDays`	No	Only include 13F filings from the last N days.
`maxConcurrency`	No	How many managers to process in parallel. SEC EDGAR's documented rate limit is 10 requests/second — keep this at or below 10.

TDQS

A4.4/5.0

Behavior4/5

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

The description and annotations consistently indicate a read-only, non-destructive operation (readOnlyHint: true, destructiveHint: false). The description adds value by detailing what data is retrieved (form, filing date, etc.) and emphasizing official, free, no-login-needed access, which aligns with openWorldHint.

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?

The description is extremely concise, using bullet-point-like dashes to front-load key features. Every word serves a purpose, from the core function to pricing and data source, without any fluff.

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 the moderate number of parameters and absence of an output schema, the description adequately covers the tool's function and parameters. It could be slightly more complete by noting that results are returned as a list of filings per manager, but this is a minor gap given the straightforward use case.

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?

The input schema covers all parameters with descriptions (100% coverage). The description adds context on how names are resolved and clarifies CIK vs. name usage, which enhances understanding beyond the schema. A perfect score is not given as the description could further detail the structure of the returned filings.

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 clearly states the tool tracks institutional managers by SEC CIK or name and retrieves 13F filings. It uses specific verbs like 'track' and 'get' with a well-defined resource (13F-HR filings), effectively distinguishing it from sibling tools like 'insider-trading-tracker' or 'sec-edgar-watcher'.

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?

The description implicitly distinguishes this tool from others (e.g., 'insider-trading-tracker') by focusing on 13F filings. However, it lacks explicit guidance on when not to use it or specific alternatives for different SEC data needs, providing only clear context for its intended use.

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

All Market and Regulatory Data Feeds — Zinin M2M Hub tools Inspect

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

Disambiguation2/5

Many tools have overlapping purposes, with over a dozen real-estate scrapers and half a dozen job boards differentiated only by geography. While descriptions are clear, an agent would struggle to pick the correct tool without prior knowledge of the specific site or region, leading to frequent misselection.

Naming Consistency2/5

Tool names use a mix of lowercase-hyphenated (boss-az, clinical-trials-monitor), underscore (pricing_info), and long descriptive phrases (official-gazette-regulatory-action-router). No consistent verb_noun pattern exists; some start with source domains, others with action nouns. This lack of predictability makes navigation confusing.

Tool Count3/5

36 tools is on the heavy side for a server that could have been more focused. While a 'data hub' can justify many endpoints, the high number of near-identical scrapers (12+ real estate, 6+ job boards) suggests bloat rather than well-scoped functionality. A leaner set with parameterized regional filters would be more appropriate.

Completeness2/5

The claimed domain 'Market and Regulatory Data Feeds' is poorly served: there are no stock/forex/commodity price feeds, few global regulatory sources (only FDA, SEC, EU tenders), and many tools are for job and property listings which are tangential. The set feels like a random aggregation rather than a coherent surface, with obvious gaps for core market and regulatory data.

Resources

Need Help?