Forecall
Failure recordsDocs
All scored servers

LeadFast: tool descriptions scored vip.leadfast/leadfast

tools/list taken
(UTC)
From
Official MCP Registry
Connected to
https://leadfast.vip/mcp
Homepage
leadfast.vip/agents
Scoring rules
v2
Removal
support@forecall.dev
Score this URL as it is today

Scores, issues and names only

This page shows how LeadFast (vip.leadfast/leadfast)'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/vip.leadfast/leadfast
Average score
41.5 / 100Cloudy
Tools
34
Near-identical descriptions
0

Across the server

  • Minor
    34 tools. Above 25, models start to tell tools apart less well.many_tools
  • Major
    23 tools repeat the same note (40 words). Say it once in the server's instructions, and let each description say what only that tool does. The note does not count toward the tools' scores.repeated_note

Tools

correct_website_facts

28 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (9 words).restates_name
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: replacement_id, facts, facts.name, facts.description, facts.audience, facts.problems, facts.exclusions, proposal_id, approved, replacement_id, facts, facts.name, facts.description, facts.audience, facts.problems, facts.exclusions, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

retry_website_review

28 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (6 words).restates_name
  • Major
    The description is too short (6 words).too_short
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: replacement_id, proposal_id, approved, replacement_id, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

select_website_offering

28 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (8 words).restates_name
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: replacement_id, url, proposal_id, approved, replacement_id, url, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

retry_research

33 / 100Rain

Purpose
6 / 20
When to use
5 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (8 words).restates_name
  • Major
    Arguments without a description: proposal_id, approved, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

cancel_website_review

35 / 100Rain

Purpose
13 / 20
When to use
0 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: replacement_id, proposal_id, approved, replacement_id, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

correct_research

35 / 100Rain

Purpose
13 / 20
When to use
0 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: corrections, proposal_id, approved, corrections, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

disconnect_integration

35 / 100Rain

Purpose
13 / 20
When to use
0 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: provider, proposal_id, approved, provider, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

test_email

35 / 100Rain

Purpose
13 / 20
When to use
0 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: proposal_id, approved, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

start_research

36 / 100Rain

Purpose
14 / 20
When to use
0 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: url, proposal_id, approved, url, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

get_match

37 / 100Rain

Purpose
17 / 20
When to use
0 / 20
Arguments
5 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: id.param_no_description
  • Minor
    String arguments with no constraint or example: id.loose_string_param
  • Minor
    Required identifiers whose description does not say where the value comes from: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

cancel_change

38 / 100Rain

Purpose
13 / 20
When to use
0 / 20
Arguments
10 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: proposal_id.param_no_description
  • Minor
    Required identifiers whose description does not say where the value comes from: proposal_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

apply_website_review

39 / 100Rain

Purpose
17 / 20
When to use
0 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: replacement_id, proposal_id, approved, replacement_id, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

connect_email

39 / 100Rain

Purpose
17 / 20
When to use
0 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: email, proposal_id, approved, email, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

connect_telegram

39 / 100Rain

Purpose
17 / 20
When to use
0 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: target, proposal_id, approved, target, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

connect_webhook

39 / 100Rain

Purpose
17 / 20
When to use
0 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: endpoint, proposal_id, approved, endpoint, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

correct_product_facts

39 / 100Rain

Purpose
17 / 20
When to use
0 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: facts, facts.name, facts.description, facts.audience, facts.problems, facts.exclusions, proposal_id, approved, facts, facts.name, facts.description, facts.audience, facts.problems, facts.exclusions, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

pause_integration

39 / 100Rain

Purpose
17 / 20
When to use
0 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: provider, proposal_id, approved, provider, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

replace_product_website

39 / 100Rain

Purpose
17 / 20
When to use
0 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: url, proposal_id, approved, url, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

test_telegram

39 / 100Rain

Purpose
17 / 20
When to use
0 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: proposal_id, approved, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

test_webhook

39 / 100Rain

Purpose
17 / 20
When to use
0 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: proposal_id, approved, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

apply_product_facts

40 / 100Cloudy

Purpose
13 / 20
When to use
5 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Arguments without a description: proposal_id, approved, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

resume_integration

40 / 100Cloudy

Purpose
13 / 20
When to use
5 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Arguments without a description: provider, proposal_id, approved, provider, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

list_matches

41 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
9 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: limit, band, since.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description

connect_slack

42 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
10 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: proposal_id, approved, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

refresh_threads

44 / 100Cloudy

Purpose
17 / 20
When to use
5 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Arguments without a description: proposal_id, approved, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

start_trial

44 / 100Cloudy

Purpose
17 / 20
When to use
5 / 20
Arguments
7 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Arguments without a description: proposal_id, approved, proposal_id, approved.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument approved is unclear.vague_boolean

get_product

46 / 100Cloudy

Purpose
6 / 20
When to use
0 / 20
Arguments
25 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (6 words).restates_name
  • Major
    The description is too short (6 words).too_short
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

get_change_status

49 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
10 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: proposal_id.param_no_description
  • Minor
    Required identifiers whose description does not say where the value comes from: proposal_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

get_monitoring_status

50 / 100Cloudy

Purpose
10 / 20
When to use
0 / 20
Arguments
25 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description is too short (7 words).too_short
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

get_product_settings

57 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
25 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

get_research

57 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
25 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

list_integrations

57 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
25 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

list_threads

57 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
25 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

get_subscription

69 / 100Cloudy

Purpose
17 / 20
When to use
5 / 20
Arguments
25 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 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