Skip to main content
Glama

WritersLogic business agents

lead-enrichment

Autonomous Lead Enrichment — Scrapes a company homepage, deduces its value proposition and buyer persona, and drafts a targeted B2B cold email.

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": {
      "url": "<url>"
    },
    "name": "lead-enrichment"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesCompany homepage URL; https:// is assumed if omitted.
senderContextNoWhat you sell, used to tailor the pitch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 burden. It usefully discloses the multi-step pipeline (fetch homepage → infer value prop and persona → draft email) and, via 'drafts', implies no email is actually sent — a meaningful side-effect clarification. However, it says nothing about network access to arbitrary URLs, latency or cost of an LLM-heavy pipeline, rate limits, or failure behavior on unreachable or JS-only pages.

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?

A single sentence that front-loads the core action and then lists the outputs in pipeline order — efficient and easy to scan. The leading 'Autonomous Lead Enrichment' label is slightly redundant with the tool name and borders on marketing framing, which keeps it from a 5.

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

Completeness4/5

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

There is no output schema, so the description must convey the return value — and it does, naming the deduced value proposition, buyer persona, and email draft as deliverables. For a two-parameter tool this is largely sufficient; only the output shape (single text blob vs. structured fields) and error handling remain unspecified.

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 (url and senderContext) are already documented, including the https:// assumption and the maxLength bounds. The description's only added nuance is that the pitch is 'targeted', which loosely maps to senderContext. Baseline 3 is appropriate when the schema does the explaining.

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 resource (a company homepage / lead) and enumerates the concrete outputs: scraped content, deduced value proposition, buyer persona, and a drafted B2B cold email. That is far more informative than the name alone. It does not differentiate against siblings, but none of the listed siblings appear to overlap, so the missing differentiation costs little.

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 explicit when-to-use or when-not-to-use guidance, no prerequisites, and no named alternatives. 'Autonomous' hints that the caller supplies only a URL, but the description never states conditions such as 'use when you have a company site and want a cold-email draft' or what to do when scraping fails.

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