Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_api_lead_verify_composite

Verify leads by checking email deliverability signals and LinkedIn profile URLs to qualify contacts before outreach.

Instructions

[Web Intelligence] Lead verification: email deliverability signals + LinkedIn URL checks Measured p50 12 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://api.caelaralabs.com.

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": {
      "email": "<email>"
    },
    "name": "caelara_api_lead_verify_composite"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesLead email address
linkedin_urlNoLinkedIn profile URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does add genuine value by disclosing measured latency (p50 12 ms, p95 15 ms with a dated source) and the upstream endpoint host, which hints at an external network call. However, it never states whether the operation is read-only, what happens if linkedin_url is malformed or unreachable, or what the verification verdict looks like.

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 compact sentences, with the functional purpose front-loaded before the performance metadata. The benchmark citation and endpoint domain are somewhat operational rather than task-oriented, but they are short and do not bury the core statement.

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 two-parameter read-style verification tool with a fully described schema and no output schema, the description covers the what but not the return semantics or error behavior. An agent knows what it verifies, but not what result to expect or how partial inputs are handled.

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 both parameters are already documented in the schema and the baseline is 3. The description only weakly adds meaning by tying linkedin_url to 'LinkedIn URL checks'; it does not clarify that linkedin_url is optional or what happens when it is absent.

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?

States a concrete verb+resource: 'Lead verification' composed of 'email deliverability signals + LinkedIn URL checks'. That is specific enough to distinguish it from narrower siblings like caelara_api_email_mx_forensics (MX records only) or caelara_api_social_card_extractor, though it never names an alternative explicitly.

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?

There is no when-to-use guidance at all: no conditions for calling it, no note on when to prefer it over the more specialized sibling tools, and no statement about when linkedin_url should be supplied versus omitted. The agent must infer all routing decisions from the name and tag alone.

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