Skip to main content
Glama

Caelara Labs Web Intelligence

lead_verify_composite

Lead verification: email deliverability signals + LinkedIn URL checks

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": "lead_verify_composite"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesLead email address
linkedin_urlNoLinkedIn profile URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It states the signals checked but does not disclose whether the operation is read-only, whether it makes external network calls, what permissions or API costs are involved, or whether results are cached.

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 a single front-loaded fragment with no wasted wording. It is terse to the point of under-specification, but the conciseness itself is effective.

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 low-complexity tool with two fully described parameters, no annotations, and no output schema, the description provides the minimum needed to understand the tool's purpose. However, it does not explain the return format or what the deliverability and LinkedIn checks actually produce, which is a meaningful gap given the absence of an output schema.

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 the baseline is 3. The description mentions email deliverability and LinkedIn checks, which lightly reinforces the meaning of the two parameters, but adds no syntax, format, or optionality semantics beyond what the schema already documents.

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?

The description names a specific action, 'Lead verification,' and specifies the two checks involved: email deliverability signals and LinkedIn URL checks. This is clear enough to distinguish it from unrelated siblings such as sitemap_crawler or html_table_parser, though it does not explicitly differentiate it from closer verification-adjacent tools like email_mx_forensics.

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 implies the tool is used to verify leads, but gives no explicit guidance on when to choose it over alternatives or when not to use it. There are no stated prerequisites, exclusions, or routing rules to another sibling tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources