Add to CRM: tool descriptions scored com.addtocrm/crm

tools/list taken: 2026-11-02 (UTC)
From: Official MCP Registry
Connected to: https://mcp.addtocrm.com/mcp
Homepage: addtocrm.com
Repository: github.com/crm-inputs/mcp
Scoring rules: v2
Removal: support@forecall.dev

Scores, issues and names only

This page shows how Add to CRM (com.addtocrm/crm)'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.addtocrm/crm

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

Across the server

No server-wide issues.

Tools

get_bulk_add_status

52 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 20 / 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_lists

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

update_crm_record

57 / 100Cloudy

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

No issues.

save_to_list

58 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 20 / 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

add_person_to_crm

60 / 100Cloudy

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

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

find_person_in_crm

60 / 100Cloudy

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

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

log_crm_activity

60 / 100Cloudy

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

Minor
String arguments with no constraint or example: title.loose_string_param
Minor
The description mentions none of its 3 or more arguments.params_not_in_description

get_account

63 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 25 / 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

get_crm_record

63 / 100Cloudy

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

Minor
The description mentions none of its 3 or more arguments.params_not_in_description

add_company_to_crm

65 / 100Cloudy

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

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

confirm_possible_match

65 / 100Cloudy

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

Minor
Required identifiers whose description does not say where the value comes from: record_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

find_company_details

65 / 100Cloudy

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

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

find_contact_details

65 / 100Cloudy

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

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

search_crm

65 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 20 / 25
Return value: 15 / 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
Minor
The description mentions none of its 3 or more arguments.params_not_in_description

search_companies

67 / 100Cloudy

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

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
No `required` list, so every argument is optional.no_required

search_prospects

67 / 100Cloudy

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

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
No `required` list, so every argument is optional.no_required

add_people_to_crm

70 / 100Clear

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 25 / 25
Return value: 15 / 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

get_profile

70 / 100Clear

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 25 / 25
Return value: 15 / 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

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