Skip to main content
Glama

get_top_shareholders_by_sector

Identify key investors in a specific sector of the Spanish stock exchange by retrieving top shareholders for sector analysis and investment research.

Instructions

Get top shareholders in a specific sector

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectorYesSector name
limitNoMaximum number of results

Implementation Reference

  • Core handler function that implements the tool logic: fetches companies in the sector, retrieves all shareholder positions, filters to sector companies, sorts by ownership percentage descending, and limits results.
    async getTopShareholdersBySector(sector: string, limit: number = 10): Promise<any[]> {
      const companies = await this.getCompaniesBySector(sector);
      const data = await this.fetchAPI('/api/shareholder-positions');
      const shareholders = data.shareholderPositions || data.positions || [];
      
      const sectorSymbols = companies.map(c => c.symbol);
      const sectorShareholders = shareholders.filter(position =>
        sectorSymbols.includes(position.company_symbol || position.ticker)
      );
    
      return sectorShareholders
        .sort((a, b) => (b.percentage || 0) - (a.percentage || 0))
        .slice(0, limit);
    }
  • src/index.ts:166-184 (registration)
    Tool registration in the listTools response, including name, description, and input schema.
    {
      name: 'get_top_shareholders_by_sector',
      description: 'Get top shareholders in a specific sector',
      inputSchema: {
        type: 'object',
        properties: {
          sector: {
            type: 'string',
            description: 'Sector name',
          },
          limit: {
            type: 'number',
            description: 'Maximum number of results',
            default: 10,
          },
        },
        required: ['sector'],
      },
    },
  • Dispatch handler in the CallToolRequestSchema switch statement that invokes the database method with parsed arguments.
    case 'get_top_shareholders_by_sector':
      result = await this.db.getTopShareholdersBySector((args as any)?.sector, (args as any)?.limit || 10);
      break;
  • Input schema defining parameters: sector (required string), limit (optional number, default 10).
    inputSchema: {
      type: 'object',
      properties: {
        sector: {
          type: 'string',
          description: 'Sector name',
        },
        limit: {
          type: 'number',
          description: 'Maximum number of results',
          default: 10,
        },
      },
      required: ['sector'],
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states a read operation ('Get'), but doesn't mention any behavioral traits such as data freshness, rate limits, authentication needs, or what 'top' means (e.g., by market cap, ownership percentage). This leaves significant gaps for a tool that likely queries financial data.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy for an agent to parse quickly.

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 the complexity of financial data queries, no annotations, and no output schema, the description is insufficient. It doesn't explain what 'top' entails, the data source, return format, or error handling. For a tool with two parameters and likely nuanced output, more context is needed to ensure reliable agent usage.

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?

The input schema has 100% description coverage, with clear documentation for 'sector' and 'limit' parameters. The description doesn't add any semantic details beyond the schema, such as examples of sector names or context for the limit. Given the high schema coverage, a baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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 the action ('Get') and target resource ('top shareholders in a specific sector'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'get_company_shareholders' or 'get_shareholder_overlap', which might have overlapping functionality, so it doesn't reach the highest score.

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 guidance on when to use this tool versus alternatives. With siblings like 'get_company_shareholders' and 'get_shareholder_overlap' that might retrieve similar data, there's no indication of context, prerequisites, or exclusions to help an agent choose appropriately.

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/anbrme/ibex35-mcp-server'

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