Skip to main content
Glama
kanto-labs

kanto-labs-mcp

Official
by kanto-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Enrich company profiles (coming soon)

enrich_company
Read-only

Turn company names, domains, emails, or URLs into rich profiles with website data, social links, and Wikidata firmographics for CRM enrichment and pre-sales research.

Instructions

COMING SOON: this Kanto Labs actor is not public on the Apify Store yet. Until it is, calls return an 'actor not yet public' error and nothing is charged. Turn domains, website URLs, email addresses or company names into company profiles. From one normal visit to the company's homepage: name, description, logo and favicon URLs, brand colour, language, the company's own social profile links (LinkedIn, X, Facebook, Instagram, YouTube, GitHub...), App Store / Google Play links and key pages (about, pricing, careers, contact, blog, docs). From Wikidata (open data): industries, country, headquarters, founding date, employee count and revenue (with the year of each figure), stock tickers, parent organization, legal form and LEI. Use it for CRM or lead-list enrichment, account research before a sales call, logo walls, market maps, or 'tell me about this company' questions. Names are matched on Wikidata (well-known organizations only); pass a domain for an exact match. Small businesses usually get the website fields only. Returns no personal data (no people, emails or phone numbers). Cost: $0.003 per company enriched, billed to your Apify account; unreachable domains, unknown names and invalid inputs are free. Runs the Apify actor kantolabs/company-enrichment with your APIFY_TOKEN; maxTotalChargeUsd caps the spend per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companiesYesOne company per item: a domain ("stripe.com"), a website URL, an email address or a company name ("Siemens"). Duplicates are removed.
timeoutSecsNoGive up after this many seconds (max 300, Apify's limit for synchronous runs). Default 280. For big batches, split the input into several calls.
includeWebsiteNoRead the company's homepage (logo, socials, apps, key pages). Default true.
maxConcurrencyNoCompanies processed in parallel. Default 10.
includeWikidataNoFirmographics from Wikidata (industry, HQ, founded, employees, revenue, ticker). Default true.
maxTotalChargeUsdNoHard spending cap for this call in USD, enforced by Apify: the run stops once it has charged this much. Default 1 (server setting KANTO_MAX_CHARGE_USD).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes far beyond annotations, disclosing the current 'coming soon' error state, zero-charge behavior until public, per-enrichment cost, free cases (unreachable domains, unknown names, invalid inputs), use of the Apify actor with APIFY_TOKEN, and the maxTotalChargeUsd safety cap. It also states a privacy guarantee (no personal data), which annotations do not cover. No contradiction with readOnlyHint=true.

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 long but information-dense; it front-loads the time-sensitive 'coming soon' caveat, then follows a logical flow from purpose to output fields to cost and auth. Some redundancy with schema (e.g., spend cap) but most sentences earn their place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and a tool of this complexity, the description covers input types, output categories, matching limitations, cost, auth, and safety cap. It addresses free and charged cases and the current non-public status, leaving no critical gap for an agent deciding whether and how to call it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptive parameter comments, but the description enriches semantics by clarifying that names only match well-known organizations on Wikidata and that domains give exact matches. It also explains cost implications of maxTotalChargeUsd, adding decision-relevant meaning beyond the schema.

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

Purpose5/5

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

The description opens with the core transformation ('Turn domains, website URLs, email addresses or company names into company profiles') and enumerates specific outputs from website and Wikidata, making the purpose unmistakable. It differentiates from sibling domain-analysis tools (lookup_domain, check_domain_authority) by focusing on company profile enrichment rather than standalone technical or SEO metrics.

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

Usage Guidelines4/5

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

Provides explicit use cases (CRM enrichment, sales research, market maps) and input guidance ('pass a domain for an exact match'; 'small businesses usually get the website fields only'). It doesn't name alternative tools or state when not to use it, but the context is clear enough for an agent to choose appropriately.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools