Skip to main content
Glama
shlomico-tr

eToro MCP Server

Official
by shlomico-tr

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
fetch_etoro_portfolioB

Fetch an eToro user's portfolio using their username

fetch_instrument_detailsB

Fetch details for a list of eToro instruments

search_instrumentsB

Search for eToro instruments by name prefix (autocomplete)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: fetch_etoro_portfolio retrieves user portfolio data, fetch_instrument_details gets details for specific instruments, and search_instruments performs autocomplete searches. There is no overlap in functionality, making tool selection straightforward for an agent.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with snake_case: fetch_etoro_portfolio, fetch_instrument_details, and search_instruments. The naming is predictable and readable throughout the set.

Tool Count3/5

With only 3 tools, the server feels thin for a financial trading domain like eToro. While the tools cover basic fetching and searching, the scope suggests more operations (e.g., trading actions, account management) would be expected, making the count borderline low.

Completeness2/5

The toolset is significantly incomplete for an eToro server. It lacks core operations such as placing trades, managing orders, viewing account details, or accessing market data beyond instruments. This creates gaps that will likely cause agent failures in real-world trading scenarios.

Maintenance

ActivityInactive
ResponsivenessNo issues