Skip to main content
Glama
Sign In
apollo-io-mcp

apollo-io-mcp

by thevgergroup
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Enrich Company

apollo_enrich_company

Enrich company details using domain or name, retrieving organizational data through Apollo match.

Instructions

Enrich a company/organization by domain or name using Apollo match.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "apollo_enrich_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
domainNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.1

TDQS

C2.8/5.0
Behavior2/5

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

No annotations provided, and the description does not disclose if enrichment is a read or write operation, any side effects, or rate limits. Only mentions the mechanism, not behavioral traits.

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?

Single concise sentence that front-loads the purpose. Could include more detail without losing conciseness, but currently no fluff.

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

Completeness3/5

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

For a simple tool with two optional parameters and no output schema, the description is minimally complete. However, it lacks explanation of what enrichment means or the expected outcome, leaving room for ambiguity.

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

Parameters2/5

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

With 0% schema description coverage, the description only mentions parameters implicitly ('by domain or name') but adds no format details, constraints, or usage notes. Minimal additional value.

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?

Description clearly states it enriches a company by domain or name using Apollo match, distinguishing from search tools but not fully from other enrich tools. The verb 'enrich' is slightly vague but acceptable.

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 on when to use this tool versus siblings like search_companies, get_complete_organization_info, or bulk_enrich. Missing context on prerequisites or alternatives.

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