Skip to main content
Glama
ceadigital-mcp-tools

ceadigital-mcp-tools

Official
by ceadigital

skip_trace_owner_phone_finder

Reveal human managing members, wireless phones, and emails behind anonymous State SOS LLCs and properties, with OFAC KYB checks in one query.

Instructions

Pierce anonymous State SOS LLCs & properties to human managing members, wireless phones, emails & OFAC KYB. (Free 1-row preview automatic when CEA_API_KEY is unset; Apify: cea_digital/skip-trace-owner-phone-finder)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "skip_trace_owner_phone_finder"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesPrimary target query, domain, URL, or identifier (default: "APEX COMMERCIAL HOLDINGS LLC")APEX COMMERCIAL HOLDINGS LLC
secondaryNoOptional secondary filter (address, condition, permit type, role keyword, or language).1201 Main St, Columbia, SC 29201

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose one genuinely valuable trait: a free 1-row preview when CEA_API_KEY is unset, implying a paid/keyed path beyond that, plus the underlying Apify actor for provenance. It says nothing about cost, rate limits, latency, or result shape (and there is no output schema to fall back on), leaving a meaningful gap for a data-collection tool.

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?

Two dense sentences with the capability front-loaded and operational caveats deferred to a parenthetical, so nothing buries the lede. Minor cost is marketing-style jargon ("Pierce", "OFAC KYB") that reads well but takes a beat to decode.

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?

The capability and preview/billing caveat are covered, and the 2-parameter surface is simple, but with no annotations and no output schema the description should say more about what a result row contains and whether calls are async. Adequate to invoke, thin on what to expect back.

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 coverage is 100%, so the baseline is 3. The description usefully implies the query should be an LLC/entity name or a property address (defaults are an LLC name and a street address), which sharpens the schema's generic "domain, URL, or identifier" wording, but it never explains the role of `secondary` beyond what the schema already says.

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?

"Pierce anonymous State SOS LLCs & properties to human managing members, wireless phones, emails & OFAC KYB" states a specific verb and resource and enumerates the exact outputs returned, which is far more informative than a name restatement. It doesn't explicitly contrast itself with the sibling scrapers, but the entity-resolution framing is distinctive enough that an agent can tell it apart from listing/transcript scrapers.

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?

The description never says when to reach for this tool versus the sibling scrapers, nor what preconditions the input must satisfy. The only conditional guidance is operational (the free preview when CEA_API_KEY is unset), not a usage rule about selecting this tool over an alternative or when not to use it.

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