mcp-server

Score a sales lead

forcedream_score_lead

Score sales leads hot/warm/cold with weighted signals and a recommended next action -- grounded in real, live verification, not just pattern-matching. Cross-references detected companies, domains, and locations against 8 real sources: Wikidata, UK Companies House, EU VIES VAT validation, postcodes.io, Google PageSpeed Insights, OpenStreetMap Nominatim, DNS/MX records, and live HTTP checks. Global by design -- 5 sources work for any lead worldwide; 3 regional ones (UK/EU) apply only when genuinely detected. SPENDS your balance -- requires authentication (OAuth). Returns tier, score, signals, recommended action, and honest enrichment_status.

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": {
      "lead_description": "<lead_description>"
    },
    "name": "forcedream_score_lead"
  }
}

Input Schema

Name	Required	Description	Default
`budget_pence`	No	Optional max spend in pence for this scoring call.
`lead_description`	Yes	Free-text description of the lead: company, contact, context, any details you have.

Output Schema

Name	Required	Description
`output`	No
`status`	Yes	'completed' or 'error'.
`verify`	No
`task_id`	No
`proof_id`	No
`balance_pence`	No
`charged_pence`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedJul 25, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, and the description adds important behavioral details: it spends balance, requires OAuth, and performs live verification against 8 sources. No contradictions with annotations.

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 relatively long but every sentence adds value, front-loading the core purpose and then detailing sources and outputs. It could be slightly more concise but is well-structured.

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

Completeness5/5

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

Given the tool's complexity (8 sources, global/regional, multiple outputs), the description is comprehensive. It covers return fields, warns about spending, and explains source behavior, leaving no major gaps.

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% with clear descriptions for both parameters. The description adds no new semantics beyond 'free-text description' and 'optional max spend', so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses specific verbs ('Score sales leads hot/warm/cold') and clearly states the resource ('sales leads') and outputs (tier, score, signals, etc.). It distinguishes from sibling tools like forcedream_check_fraud and forcedream_extract_data by focusing on lead scoring.

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

Usage Guidelines4/5

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

The description implies usage for scoring any sales lead and mentions costs and authentication, but does not explicitly compare with siblings or state when not to use it. However, the global/regional sourcing note provides some usage context.

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

All mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.