Skip to main content
Glama

alphapulse

Discover and analyze trading signal providers, copy traders, expert advisors, and managed accounts with AI-synthesized rankings and due diligence. Access real-time alternative trading intelligence across global markets.

Instructions

AlphaPulse: Global alternative trading intelligence API. AI-synthesized signal provider rankings, managed account analysis, copy trading discovery, expert advisor (EA/robot) vetting, multi-asset arbitrage, crypto

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNolang
typeNosignal|copy|EA|managed|vault|any
actionYesWhich endpoint to call. Options: discover | signals | ea | copy | managed | vaults | vet | broker | asia | alternative | compare
regionNoregion
min_tvlNomin_tvl
categoryNocategory
platformNoplatform
protocolNoprotocol
providerNoprovider
strategyNostrategy
use_caseNouse_case
min_weeksNomin_weeks
providersNoComma-separated provider names (min 2)
instrumentNoinstrument
min_returnNomin_return
min_copiersNomin_copiers
max_drawdownNomax_drawdown
us_accessibleNous_accessible
min_investmentNomin_investment
min_track_recordNomin_track_record
Behavior2/5

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

No annotations provided; description carries full burden. It mentions pricing per endpoint and global coverage but does not disclose error behavior, rate limits, authentication needs, or read-only nature.

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 lengthy with a bullet list of endpoints and prices. It is somewhat structured but contains redundancy (e.g., 'Coverage: Global') and could be more concise.

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?

Given no output schema and 20 parameters, the description does not explain what the tool returns or how parameters like 'min_tvl' filter results. It is incomplete for effective tool selection.

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 coverage is 100% with parameter descriptions, but those descriptions are minimal (e.g., 'lang' is just 'lang'). The tool description adds context for the 'action' parameter listing endpoints, but other parameters lack additional meaning beyond names.

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 states it is a global alternative trading intelligence API with multiple endpoints (discover, signals, ea, etc.), distinguishing it from sibling 'pulse' tools by specifying its domain.

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?

No guidance on when to use this tool versus other 'pulse' tools. It lists endpoints but does not provide criteria for selection or when to avoid.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GTCC777/mcp-pulsenetwork'

If you have feedback or need assistance with the MCP directory API, please join our Discord server