Skip to main content
Glama

get_directors_by_name

Search for directors by name across all companies in the Spanish stock exchange to analyze corporate relationships.

Instructions

Search for directors by name across all companies

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDirector name or partial match

Implementation Reference

  • The core handler function that executes the tool logic by fetching network data from the API and filtering directors by the provided name.
    async getDirectorsByName(name: string): Promise<any[]> {
      const data = await this.fetchAPI('/api/network');
      const directors = data.directors || [];
      return directors.filter(director => 
        director.name && director.name.toLowerCase().includes(name.toLowerCase())
      );
    }
  • Defines the tool's input schema, including the required 'name' parameter for searching directors.
    {
      name: 'get_directors_by_name',
      description: 'Search for directors by name across all companies',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'Director name or partial match',
          },
        },
        required: ['name'],
      },
    },
  • src/index.ts:601-603 (registration)
    Registers the tool handler in the CallToolRequestSchema switch statement, delegating to the database method.
    case 'get_directors_by_name':
      result = await this.db.getDirectorsByName((args as any)?.name);
      break;
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the search function but lacks critical details: whether it's case-sensitive, supports fuzzy matching, returns partial matches as implied by the schema, includes pagination or limits, requires authentication, or has rate limits. For a search tool with zero annotation coverage, this is a significant gap in transparency.

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 front-loads the core purpose ('Search for directors by name') and adds necessary context ('across all companies'). There is zero wasted language, and every word earns its place by clarifying scope and action.

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 tool's complexity (a search function with no output schema and no annotations), the description is incomplete. It lacks details on return values (e.g., format, fields like director IDs or company affiliations), behavioral traits (e.g., search precision, result limits), and usage context. For a tool with 1 parameter but no structured output or safety annotations, the description should provide more operational context.

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 the 'name' parameter documented as 'Director name or partial match'. The description adds no additional parameter semantics beyond what's in the schema. According to the 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 ('search') and resource ('directors by name'), specifying it searches across all companies. It distinguishes from siblings like 'get_company_directors' (which likely returns directors for a specific company) by emphasizing the cross-company scope. However, it doesn't explicitly differentiate from other search tools like 'analyze_natural_query' or 'execute_custom_query' that might also handle director searches.

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. It doesn't mention prerequisites (e.g., needing a name input), exclusions (e.g., not for filtering by other criteria), or comparisons to siblings like 'get_company_directors' (for company-specific searches) or 'get_board_interlocks' (for relationship analysis). Usage is implied by the name but not explicitly stated.

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