pulsenetwork

alphapulse

AlphaPulse: The due-diligence layer for traders and allocators, worldwide — check before you fund. Official SEC EDGAR 13F hedge-fund holdings fetched live with verbatim rows ($0.50), prop-firm shortlists with payout-proof checks ($0.15), broker recommendations, EA/signal-provider/copy-trading discovery and vetting, managed accounts, DeFi vaults — forex, CFDs, futures, stocks, crypto. 13 endpoints.

Coverage: Global

Endpoints: • discover ($0.15): Cross-platform provider discovery • signals ($0.10): Signal provider discovery • ea ($0.10): Expert Advisor discovery • copy ($0.10): Copy trading discovery • managed ($0.10): Managed account discovery • vaults ($0.08): DeFi vault discovery • vet ($0.15): Provider due diligence • broker ($0.10): IB-approved broker recommendation • asia ($0.08): Asia-Pacific copy trading discovery • alternative ($0.08): Alternative and niche strategies • compare ($0.10): Side-by-side provider comparison • fund-check ($0.50): Hedge fund holdings check — official SEC 13F, live • prop-firms ($0.15): Prop-firm shortlist — payout-proof first, region-aware • fund-check-lite ($0.25): Hedge fund holdings check (lite/preview) — official SEC 13F, live, $0.25

Input Schema

TableJSON Schema

Name	Required	Description
`cik`	No	optional — SEC CIK if known
`top`	No	holdings rows to return, 5-25 (default 15)
`fund`	No	manager/fund name to look up in EDGAR
`lang`	No	lang
`type`	No	signal\|copy\|EA\|managed\|vault\|any
`style`	No	style constraints — news trading, EAs, weekend holds
`action`	Yes	Which endpoint to call. Options: discover \| signals \| ea \| copy \| managed \| vaults \| vet \| broker \| asia \| alternative \| compare \| fund-check \| prop-firms \| fund-check-lite
`market`	No	forex \| cfd \| futures \| stocks \| crypto
`region`	No	region
`min_tvl`	No	min_tvl
`category`	No	category
`platform`	No	platform
`protocol`	No	protocol
`provider`	No	provider
`strategy`	No	strategy
`use_case`	No	use_case
`min_weeks`	No	min_weeks
`providers`	No	Comma-separated provider names (min 2)
`instrument`	No	instrument
`min_return`	No	min_return
`min_copiers`	No	min_copiers
`max_drawdown`	No	max_drawdown
`us_accessible`	No	us_accessible
`min_investment`	No	min_investment
`min_track_record`	No	min_track_record

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedJul 25, 2026

changedInput schema / properties / action / description

Previous value: -"Which endpoint to call. Options: discover | signals | ea | copy | managed | vaults | vet | broker | asia | alternative | compare | fund-check | prop-firms"New value: +"Which endpoint to call. Options: discover | signals | ea | copy | managed | vaults | vet | broker | asia | alternative | compare | fund-check | prop-firms | fund-check-lite"

changedInput schema / properties / action / enum

Previous value: -[
-  "discover",
-  "signals",
-  "ea",
-  "copy",
-  "managed",
-  "vaults",
-  "vet",
-  "broker",
-  "asia",
-  "alternative",
-  "compare",
-  "fund-check",
-  "prop-firms"
-]New value: +[
+  "discover",
+  "signals",
+  "ea",
+  "copy",
+  "managed",
+  "vaults",
+  "vet",
+  "broker",
+  "asia",
+  "alternative",
+  "compare",
+  "fund-check",
+  "prop-firms",
+  "fund-check-lite"
+]

Changed7 schema fields changedJul 10, 2026

changedInput schema / properties / action / description

Previous value: -"Which endpoint to call. Options: discover | signals | ea | copy | managed | vaults | vet | broker | asia | alternative | compare"New value: +"Which endpoint to call. Options: discover | signals | ea | copy | managed | vaults | vet | broker | asia | alternative | compare | fund-check | prop-firms"

changedInput schema / properties / action / enum

Previous value: -[
-  "discover",
-  "signals",
-  "ea",
-  "copy",
-  "managed",
-  "vaults",
-  "vet",
-  "broker",
-  "asia",
-  "alternative",
-  "compare"
-]New value: +[
+  "discover",
+  "signals",
+  "ea",
+  "copy",
+  "managed",
+  "vaults",
+  "vet",
+  "broker",
+  "asia",
+  "alternative",
+  "compare",
+  "fund-check",
+  "prop-firms"
+]

addedInput schema / properties / cik

Added value: +{
+  "description": "optional — SEC CIK if known",
+  "type": "string"
+}

addedInput schema / properties / fund

Added value: +{
+  "description": "manager/fund name to look up in EDGAR",
+  "type": "string"
+}

addedInput schema / properties / market

Added value: +{
+  "description": "forex | cfd | futures | stocks | crypto",
+  "type": "string"
+}

addedInput schema / properties / style

Added value: +{
+  "description": "style constraints — news trading, EAs, weekend holds",
+  "type": "string"
+}

addedInput schema / properties / top

Added value: +{
+  "description": "holdings rows to return, 5-25 (default 15)",
+  "type": "string"
+}

First observedJul 6, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds useful context like endpoint-specific pricing (e.g., '$0.50' for fund-check) and live data fetching for SEC 13F records. However, it omits rate limits, authentication requirements, error behavior, return format, and data freshness beyond 'live' for some endpoints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is structured with a clear upfront value proposition followed by a bulleted endpoint list, which aids scannability. However, it includes marketing fluff ('check before you fund') and repeats 'discovery' across many endpoints, adding wordiness. It earns a middle score: efficient organization but not every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex 25-parameter tool with 14 endpoint actions, yet the description fails to explain which parameters apply to which endpoint. For example, an agent cannot determine whether 'cik' is only for fund-check or if 'min_copiers' applies to copy. There is no output schema and no description of the response format, leaving a significant gap in operational understanding.

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%, so the baseline is 3. The description does not add any parameter-level semantics beyond what the schema provides, and the schema descriptions are often unhelpful (e.g., 'lang', 'region', 'min_tvl' with no explanation of allowed values or formats). The description could have mapped parameters to endpoints, but doesn't.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies AlphaPulse as a due-diligence layer for traders, listing specific services such as SEC EDGAR 13F holdings and prop-firm shortlists. It has a specific verb ('check before you fund') and a resource (financial providers and funds). However, it does not differentiate from sibling tools beyond being finance-focused, and the broad endpoint list makes it somewhat ambiguous what the core action is.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit guidance on when to use AlphaPulse versus sibling tools like cryptopulse or marketpulse. The endpoint list gives implied usage (e.g., 'fund-check' for 13F filings), but there is no statement of alternatives or exclusions. An agent would struggle to decide between AlphaPulse and similar Pulse tools without additional context.

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

All pulsenetwork 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.2/5.0

Disambiguation4/5

Each tool has a unique domain prefix (e.g., airdroppulse, alphapulse, arbipulse) making them mostly distinguishable at a glance. A few adjacent verticals like careerpulse vs talentpulse or marketpulse vs dealpulse have overlapping themes, but their descriptions clarify the distinct focus. The utility tools (catalog_search, discover, get_openapi_spec, x402_troubleshoot) are also clearly distinct in role. However, the sheer number of similar 'pulse' names could still cause misselection without reading descriptions.

Naming Consistency4/5

The dominant naming convention is `<domain>pulse` (e.g., climatepulse, cryptopulse, edupulse), which is highly consistent and predictable. Exceptions like catalog_search, discover, get_openapi_spec, x402_troubleshoot, and stateedge break the pattern, but these are few and serve obvious utility purposes. Overall, the convention is clear and easily learnable.

Tool Count2/5

With 80 tools, the server presents an extremely large and potentially overwhelming surface. While each tool represents a distinct intelligence vertical and navigation aids exist (catalog_search, discover, get_openapi_spec), the count far exceeds the typical 3-15 range for coherent agent use and even the 'heavy' 16-25 range. The burden of selecting the correct vertical from 80 options is significant, despite clear naming.

Completeness5/5

The server offers an exceptionally broad and deep coverage of domains, from finance and health to agriculture and gaming. Each vertical includes multiple endpoints that address core operations for its domain, such as search, analysis, comparisons, deterministic checks, and even action-oriented tools like letter generators and physical mail. The presence of free discovery and troubleshooting tools fills potential gaps, leaving no obvious dead ends in the overall tool surface.

alphapulse

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources