Leadgen ONRC Romania: tool descriptions scored com.adrianhomelab/leadgen-onrc

tools/list taken: 2026-11-02 (UTC)
From: Official MCP Registry
Connected to: https://leadgen-mcp.adrianhomelab.com/mcp?src=mcp-registry
Homepage: leadgen.adrianhomelab.com
Repository: github.com/darksider4all/leadgen-mcp
Scoring rules: v2
Removal: support@forecall.dev

Scores, issues and names only

This page shows how Leadgen ONRC Romania (com.adrianhomelab/leadgen-onrc)'s tool descriptions scored, the issues found and the names of its tools and parameters. The descriptions are the server's own: read them where the copy came from.

Forecall asked the URL this server lists in the official MCP Registry for its tools/list once, on the date above, without calling any tool. The server may have changed since.

servers/com.adrianhomelab/leadgen-onrc

Average score: 66.4 / 100Cloudy
Tools: 18
Near-identical descriptions: 0

Across the server

Minor
The server's instructions are 2609 characters. Claude Code reads only the first 2,048 by default (Codex 0.154.0 reads them whole). Put what the server is for first.instructions_long

Tools

lookup_financials

55 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 18 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

extract_contacts

58 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 18 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

lookup_financial_ratios

60 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 18 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

watch_caen

60 / 100Cloudy

Purpose: 17 / 20
When to use: 5 / 20
Arguments: 18 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

No issues.

lookup_domain

63 / 100Cloudy

Purpose: 20 / 20
When to use: 5 / 20
Arguments: 18 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

No issues.

watch_company

63 / 100Cloudy

Purpose: 20 / 20
When to use: 5 / 20
Arguments: 18 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

No issues.

list_watches

65 / 100Cloudy

Purpose: 20 / 20
When to use: 5 / 20
Arguments: 25 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 0 / 10

No issues.

lookup_by_category

65 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 20 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

match_companies

65 / 100Cloudy

Purpose: 17 / 20
When to use: 5 / 20
Arguments: 23 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

No issues.

unwatch

65 / 100Cloudy

Purpose: 20 / 20
When to use: 5 / 20
Arguments: 20 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

Minor
No `required` list, so every argument is optional.no_required

find_company_by_domain

68 / 100Cloudy

Purpose: 20 / 20
When to use: 5 / 20
Arguments: 18 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

No issues.

poll_watchlist

69 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 25 / 25
Return value: 15 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

report_issue

70 / 100Clear

Purpose: 20 / 20
When to use: 5 / 20
Arguments: 20 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

No issues.

lookup_business

72 / 100Clear

Purpose: 17 / 20
When to use: 5 / 20
Arguments: 18 / 25
Return value: 15 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

No issues.

lookup_companies

72 / 100Clear

Purpose: 17 / 20
When to use: 5 / 20
Arguments: 23 / 25
Return value: 15 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

No issues.

get_usage

73 / 100Clear

Purpose: 20 / 20
When to use: 10 / 20
Arguments: 25 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 0 / 10

No issues.

enrich_company

75 / 100Clear

Purpose: 17 / 20
When to use: 20 / 20
Arguments: 18 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

No issues.

lookup_director

78 / 100Clear

Purpose: 20 / 20
When to use: 15 / 20
Arguments: 18 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

No issues.

What static scoring cannot tell

This score reads only the text of each description and schema: it says what is written, not what a model will do. Short tools whose names already say what they do, such as browser_close, score low here even when models use them well, and in our measurements current models chose the right tool in one step even from one-line descriptions, as long as the names and schemas differed. What the text cannot show, such as what happens over several steps and whether an added sentence helps or misleads, is what an evaluation measures, on the Pro and Team plans.

Is your server listed here and you would rather it were not? Email support@forecall.dev, and we will take it off within 7 days.

All scored servers