Skip to main content
Glama

get_company_directors

Retrieve board director information for companies on the Spanish stock exchange by providing a company ID.

Instructions

Get board directors for a specific company

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyIdYesCompany ID or use get_company_by_symbol first to get ID

Implementation Reference

  • src/index.ts:106-119 (registration)
    Tool registration including name, description, and input schema definition.
    {
      name: 'get_company_directors',
      description: 'Get board directors for a specific company',
      inputSchema: {
        type: 'object',
        properties: {
          companyId: {
            type: 'string',
            description: 'Company ID or use get_company_by_symbol first to get ID',
          },
        },
        required: ['companyId'],
      },
    },
  • MCP tool dispatch handler that calls the database method with companyId argument.
    case 'get_company_directors':
      result = await this.db.getCompanyDirectors((args as any)?.companyId);
      break;
  • Core implementation fetching network data from API and filtering directors by company ID.
    async getCompanyDirectors(companyId: string): Promise<any[]> {
      const data = await this.fetchAPI('/api/network');
      const directors = data.directors || [];
      return directors.filter(director => director.company_id === companyId);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does but doesn't describe how it behaves: no information about return format (e.g., list of directors with details), pagination, rate limits, authentication needs, or error handling. For a read operation with no annotation coverage, this leaves significant gaps in understanding the tool's behavior.

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 states the core purpose without unnecessary words. It's appropriately sized for a simple lookup tool and front-loaded with the essential information. Every word earns its place in this concise formulation.

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 annotations, no output schema, and a simple but undocumented return type, the description is incomplete. It doesn't explain what the tool returns (e.g., list of director objects with fields like name, title, tenure) or any behavioral aspects. For a tool that presumably returns structured data about directors, more context about the response format would be helpful.

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 description coverage is 100% with one parameter clearly documented in the schema. The description adds no additional parameter semantics beyond what's in the schema. According to scoring rules, with high schema coverage (>80%), the baseline is 3 even with no param info in the description, which applies here.

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 verb 'Get' and resource 'board directors for a specific company', making the purpose immediately understandable. It distinguishes from siblings like get_company_shareholders or get_directors_by_name by specifying it's about board directors for a company. However, it doesn't explicitly differentiate from get_all_companies or get_company_by_symbol beyond the resource focus.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when you need board directors for a company, but provides no explicit guidance on when to use this versus alternatives like get_directors_by_name or get_company_shareholders. The input schema suggests using get_company_by_symbol first to get the ID, which offers some implied context, but the description itself lacks clear when/when-not instructions.

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