ibex35-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Name | Description |
|---|---|
| get_all_companiesB | Get all IBEX 35 companies with current prices and key metrics |
| get_company_by_symbolC | Get detailed information for a specific company by its stock symbol |
| get_companies_by_sectorC | Get companies filtered by sector |
| get_companies_with_pe_ratioB | Get companies filtered by P/E ratio range |
| get_company_directorsB | Get board directors for a specific company |
| get_board_interlocksA | Find directors who serve on multiple IBEX 35 company boards |
| get_directors_by_nameC | Search for directors by name across all companies |
| get_company_shareholdersC | Get shareholders for a specific company |
| get_shareholder_overlapB | Find shareholders who own stakes in multiple IBEX 35 companies |
| get_top_shareholders_by_sectorC | Get top shareholders in a specific sector |
| get_historical_pricesB | Get historical price data for a company |
| get_top_performersC | Get top performing stocks over a specified period |
| get_recent_newsB | Get recent news articles, optionally filtered by company |
| get_news_by_sentimentC | Get news articles filtered by sentiment |
| get_lobbying_meetingsC | Get EU lobbying meetings, optionally filtered by company |
| get_most_active_lobbyistsC | Get organizations with the most EU lobbying meetings |
| get_esg_scoresC | Get ESG (Environmental, Social, Governance) scores |
| get_weekly_reportsB | Get generated weekly reports and analysis |
| get_network_analysisB | Get comprehensive network analysis of board interlocks and shareholder relationships |
| get_sector_correlation_analysisC | Analyze sector performance correlations and market trends |
| analyze_natural_queryC | Process and execute complex natural language queries about companies, financials, governance, or markets |
| compare_companiesC | Compare multiple companies across various metrics (financial, governance, market performance) |
| analyze_trendsC | Analyze trends in stock prices, market performance, or sector movements over time |
| assess_investment_riskC | Comprehensive risk assessment for companies or sectors including market, governance, and operational risks |
| generate_analyst_reportC | Generate a comprehensive analyst report for a company, sector, or market theme |
| screen_opportunitiesC | Screen for investment opportunities based on specific criteria (value, growth, dividend, ESG, etc.) |
| execute_custom_queryB | Execute a custom SQL query on the database (SELECT only) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 27 tools
The tools have clear individual purposes, but there is significant functional overlap that could cause confusion. For example, 'analyze_trends', 'get_sector_correlation_analysis', and 'get_weekly_reports' all involve trend analysis, while 'get_all_companies', 'get_companies_by_sector', and 'get_companies_with_pe_ratio' are variations of company filtering. Descriptions help differentiate, but the boundaries are not always distinct.
Most tools follow a consistent verb_noun pattern (e.g., 'get_company_directors', 'analyze_trends'), with clear action-oriented prefixes like 'get_', 'analyze_', or 'assess_'. However, there are minor deviations such as 'execute_custom_query' (which uses 'execute' instead of 'get') and 'screen_opportunities' (which uses 'screen' as a verb), slightly breaking the pattern but remaining readable.
With 27 tools, the set feels overly heavy and potentially redundant for the IBEX 35 financial analysis domain. Many tools could be consolidated (e.g., multiple 'get_' queries for companies), leading to a bloated interface that may overwhelm agents and increase misselection risk, despite the broad scope.
The tool surface is highly complete for financial and governance analysis of IBEX 35 companies. It covers data retrieval (e.g., company info, prices, news), analysis (e.g., trends, risk, reports), and screening (e.g., opportunities), with no obvious gaps. Agents can perform comprehensive workflows from basic queries to advanced analytics without dead ends.