[Sales Intelligence] Enrich a single company with domain, description, industry, employee band, social profiles, and (where available) email patterns.
Wraps nexgendata/company-enrichment-tool. Accepts either a free-form
company name ("Stripe") or a domain ("stripe.com").
Args: domain_or_name: Company name or domain.
| Name | Required | Description | Default |
|---|---|---|---|
| domain_or_name | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description lists the returned data fields and explains the input flexibility (name or domain). Annotations already indicate readOnlyHint and openWorldHint, and the description adds context about the tool's wrapper and behavior. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences plus a parameter doc line, efficiently conveying purpose, input, output, and reference. No unnecessary words, well front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity (one param, no output schema), the description covers all needed information: what it does, what it returns, and input format. It is complete for its complexity level.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter 'domain_or_name' has a schema with 0% description coverage. The description fully explains its meaning: accepts either a company name or domain. This adds complete semantic value beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states that the tool enriches a single company with specific data fields (domain, description, industry, employee band, social profiles, email patterns). It also details the input format (company name or domain). This distinguishes it from siblings like enrich_lead_list which handles multiple records.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use (single company enrichment) but does not explicitly mention when not to use or compare with alternatives like aggregate_company_profile or enrich_lead_list. Usage context is suggested but not fully explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Many tools have overlapping functionality across categories (e.g., multiple search_arxiv, search_google_scholar, real estate tools, DNS/WHOIS checks). An agent would struggle to differentiate between similar tools from different categories, leading to ambiguity.
Tools follow a 'category__verb_noun' pattern mostly, but verbs vary (get, search, screen, check, etc.) and some categories use different orders (e.g., 'get_repo_stats' vs 'search_repos'). The consistency is acceptable but not uniform across the entire set.
With 152 tools, the server is excessively large for a single MCP server. While it aims to be an all-in-one gateway, the sheer number overwhelms the agent and likely exceeds practical limits for coherent selection.
The server covers a wide range of domains (finance, real estate, news, developer tools, etc.) but has notable gaps (e.g., social media APIs, CRM tools). Coverage is broad but not exhaustive, and some niche areas (e.g., global stock exchanges) are over-represented.