Skip to main content
Glama
luarss

alternativespe-mcp

by luarss

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ALTDMP_API_KEYYesYour Alternatives Partner API key
ALTDMP_BASE_URLNoAPI base URL overridehttps://api.altdmp.io/v3

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_capital_receiversA

List/filter capital receivers (funded companies / startups) in Southeast Asia. Supports filters, search, ordering and pagination.

get_capital_receiverB

Get a capital receiver (company) detail by UUID: financials, cap table, investors, deals and news.

search_capital_allocatorsB

List/filter capital allocators (investors: VC/PE firms, corporates, family offices).

get_capital_allocatorA

Get a capital allocator (investor) detail by UUID: investments, AUM, commitments, financials, cap table, funds and news.

search_fundsB

List/filter funds. (Atlas subscription tier only.)

get_fundA

Get a fund detail by UUID: performance, AUM, commitments, investments and news.

search_peopleC

List/filter people (founders, directors, key executives).

get_personA

Get a person detail by UUID: roles, investments and news.

search_service_providersA

List/filter service providers (auditors, legal and professional services firms).

search_investorsB

Cross-entity investor lookup / discovery across allocators, funds and people.

get_reference_dataA

Get reference data: enums, countries, industries, themes and other controlled vocabularies used by filter fields.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 11 tools

Disambiguation4/5

Most tools are clearly separated by entity type (capital_receivers, capital_allocators, funds, people, service_providers) and action (search vs get). The only potential confusion is between search_capital_allocators and search_investors, since both relate to investors, but search_investors is explicitly cross-entity, which helps.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern: get_<entity> for detail retrieval and search_<entity> for list/filter operations. The naming is predictable and uniform across the entire set.

Tool Count4/5

11 tools is within the well-scoped range. The count is reasonable for a data-discovery API covering multiple entity types, though it could be slightly leaner if some search tools were consolidated.

Completeness4/5

The tool surface covers search and detail retrieval for the main entities (people, capital receivers, capital allocators, funds, service providers) plus reference data. Missing operations like creating or updating entities are not expected for a read-only data provider, so the coverage is appropriate. A minor gap is the lack of a dedicated get_service_provider detail tool, but search_service_providers may suffice.

Maintenance

ActivityMaintained
ResponsivenessNo issues