Skip to main content
Glama

LeadSail — Software Growth Engine

Angry Competitor Radar

radar_scan
Read-only

Turn Product Hunt product slugs into reachable contacts: finds the maker, their website and public email, checks MX and the outbound gateway's cleaning verdict, and returns evidence links. Requires an X-Api-Key header from a LeadSail account (same key and quota as the REST API).

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": {
      "slugs": "<slugs>"
    },
    "name": "radar_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax leads to return (1-20, default 5)
slugsYesProduct Hunt product slugs (max 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the genuinely useful operational facts: an X-Api-Key header is required, the key and quota are shared with the REST API, and the tool performs external MX and gateway-cleaning lookups. It still omits what happens when a lookup fails or an email is not found.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the verb and outcome, then the auth prerequisite. No filler.

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?

With no output schema, the description usefully enumerates what comes back (maker, website, public email, evidence links), and it covers the auth requirement. For a two-parameter, open-world read tool that is nearly complete, though error and partial-result behavior remain unstated.

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% (slugs and limit, both documented with ranges and limits), so the schema already carries parameter meaning. The description only restates that inputs are Product Hunt product slugs and adds no format caveats such as slug syntax or case handling.

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 concrete input (Product Hunt product slugs) and a concrete output (maker, website, public email, MX and cleaning verdict, evidence links), so the agent knows exactly what the tool produces. It does not reconcile the fanciful title 'Angry Competitor Radar' with the actual enrichment behavior, and it never contrasts itself with its siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the slug-to-contact framing and the mention of the LeadSail key/quota, but there is no explicit 'use this when' statement, no exclusions, and no alternative named. An agent must infer that this is the lead-enrichment path rather than, say, the audit path.

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