Skip to main content
Glama
phxdev1

People Data Labs MCP Server

enrich_company

Enhance company profiles by adding crucial data such as social media links, stock tickers, and website details. Input company name, website, profiles, or ticker for comprehensive enrichment.

Instructions

Enrich a company profile with additional data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName of the company
profileNoSocial media profile URLs of the company
tickerNoStock ticker symbol of the company
websiteNoWebsite of the company

Implementation Reference

  • The main execution logic for the 'enrich_company' tool: validates arguments using isValidCompanyEnrichArgs, constructs query parameters, calls the People Data Labs /company/enrich API endpoint, and returns the response as formatted JSON.
    private async handleEnrichCompany(args: any) {
      if (!isValidCompanyEnrichArgs(args)) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Invalid company enrichment parameters. Must provide at least one identifier (name, website, profile, or ticker).'
        );
      }
    
      const params: Record<string, any> = {};
      
      // Add parameters to the request
      if (args.name) params.name = args.name;
      if (args.website) params.website = args.website;
      if (args.profile) params.profile = args.profile;
      if (args.ticker) params.ticker = args.ticker;
    
      const response = await pdlApi.get('/company/enrich', { params });
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • src/index.ts:220-253 (registration)
    Registers the 'enrich_company' tool in the MCP server's tool list, including name, description, and detailed input schema defining properties and required fields via anyOf.
    {
      name: 'enrich_company',
      description: 'Enrich a company profile with additional data',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'Name of the company',
          },
          website: {
            type: 'string',
            description: 'Website of the company',
          },
          profile: {
            type: 'array',
            items: {
              type: 'string'
            },
            description: 'Social media profile URLs of the company',
          },
          ticker: {
            type: 'string',
            description: 'Stock ticker symbol of the company',
          },
        },
        anyOf: [
          { required: ['name'] },
          { required: ['website'] },
          { required: ['profile'] },
          { required: ['ticker'] },
        ],
      },
    },
  • Type guard function that validates company enrichment arguments, ensuring at least one identifier (name, website, profile, or ticker) is provided.
    const isValidCompanyEnrichArgs = (args: any): args is {
      name?: string;
      website?: string;
      profile?: string[];
      ticker?: string;
    } => {
      if (typeof args !== 'object' || args === null) {
        return false;
      }
    
      // Check if at least one identifier is provided
      const hasIdentifier =
        typeof args.name === 'string' ||
        typeof args.website === 'string' ||
        (Array.isArray(args.profile) && args.profile.length > 0) ||
        typeof args.ticker === 'string';
    
      return hasIdentifier;
    };
  • src/index.ts:404-405 (registration)
    Routes 'enrich_company' tool calls to the handleEnrichCompany method in the CallToolRequestSchema handler.
    case 'enrich_company':
      return await this.handleEnrichCompany(request.params.arguments);
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. It mentions 'enrich' but doesn't disclose if this is a read-only lookup, requires authentication, has rate limits, or what happens on failure. For a tool with no annotations, this is a significant gap in behavioral context.

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. There's no wasted text, and it's appropriately sized for the tool's complexity, 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 no annotations, no output schema, and a tool that likely returns enriched data, the description is incomplete. It doesn't explain what 'additional data' includes, the format of results, or error handling. For a data enrichment tool with these gaps, more context is needed to be fully 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 clear parameter descriptions in the schema. The tool description adds no additional meaning about parameters beyond implying they're inputs for enrichment. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action ('enrich') and resource ('company profile'), but it's vague about what 'additional data' means. It doesn't differentiate from sibling tools like 'search_companies' or 'bulk_person_enrich', which might also provide company data. The purpose is understandable but lacks specificity.

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?

No guidance is provided on when to use this tool versus alternatives like 'search_companies' or 'enrich_person'. The description implies it's for enhancing existing company profiles, but it doesn't specify prerequisites, context, or exclusions, leaving the agent to guess based on tool names alone.

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

Related 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/phxdev1/peopledatalabs-mcp'

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