Skip to main content
Glama
Cyreslab-AI

Crunchbase MCP Server

get_company_details

Retrieve comprehensive details about a company by providing its name or UUID, using Crunchbase MCP Server data for accurate insights.

Instructions

Get detailed information about a specific company

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
name_or_idYesCompany name or UUID

Implementation Reference

  • MCP tool call handler for 'get_company_details' that validates input, calls CrunchbaseAPI.getCompanyDetails, and returns JSON stringified company details.
    case 'get_company_details': {
      if (!args || typeof args !== 'object' || !('name_or_id' in args) || typeof args.name_or_id !== 'string') {
        throw new McpError(ErrorCode.InvalidParams, 'Missing or invalid name_or_id parameter');
      }
      const params: GetCompanyDetailsInput = { name_or_id: args.name_or_id };
      const company = await this.crunchbaseApi.getCompanyDetails(params);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(company, null, 2),
          },
        ],
      };
    }
  • Core implementation of getCompanyDetails: searches for company by name_or_id to get UUID, then fetches detailed company data from Crunchbase API.
    async getCompanyDetails(params: GetCompanyDetailsInput): Promise<Company> {
      try {
        // First, try to search for the company by name
        const searchResponse = await this.client.get<CrunchbaseApiResponse<Company[]>>('/searches/organizations', {
          params: {
            query: params.name_or_id,
            limit: 1
          }
        });
    
        if (searchResponse.data.count === 0) {
          throw new Error(`Company not found: ${params.name_or_id}`);
        }
    
        const companyId = searchResponse.data.data[0].uuid;
    
        // Then, get the detailed information using the UUID
        const detailsResponse = await this.client.get<Company>(`/entities/organizations/${companyId}`);
        return detailsResponse.data;
      } catch (error) {
        console.error('Error getting company details:', error);
        throw this.handleError(error);
      }
    }
  • src/index.ts:230-242 (registration)
    Tool registration in ListToolsRequestSchema handler, including name, description, and input schema.
      name: 'get_company_details',
      description: 'Get detailed information about a specific company',
      inputSchema: {
        type: 'object',
        properties: {
          name_or_id: {
            type: 'string',
            description: 'Company name or UUID',
          },
        },
        required: ['name_or_id'],
      },
    },
  • TypeScript interface defining the input schema for get_company_details tool.
    export interface GetCompanyDetailsInput {
      name_or_id: string;
    }
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 this is a read operation ('Get'), but doesn't mention authentication needs, rate limits, error handling, or what format the 'detailed information' returns. This leaves significant gaps for a tool that presumably queries external data.

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

Conciseness4/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 fluff. It's appropriately sized for a simple lookup tool, though it could be slightly more informative without losing conciseness.

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 and no output schema, the description is incomplete for a tool that fetches 'detailed information'. It doesn't explain what details are returned, potential limitations, or how it differs from sibling tools. For a data retrieval tool with external dependencies, this leaves too many unknowns.

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%, so the input schema already documents the single parameter 'name_or_id' as 'Company name or UUID'. The description adds no additional meaning about the parameter (e.g., examples, formatting, or how it's used), so it meets the baseline of 3 where the schema does the heavy lifting.

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 detailed information') and resource ('about a specific company'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'search_companies' or specify what constitutes 'detailed information' versus what other tools might provide.

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 'get_acquisitions'. The description implies it's for retrieving details about a known company, but it doesn't specify prerequisites (e.g., needing the company name/UUID) or exclusions (e.g., not for searching).

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/Cyreslab-AI/crunchbase-mcp-server'

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