io.inboxguard/email-deliverability: tool descriptions scored

tools/list taken: 2026-11-02 (UTC)
From: Official MCP Registry
Connected to: https://mcp.inboxguard.io/mcp
Scoring rules: v2
Removal: support@forecall.dev

Scores, issues and names only

This page shows how io.inboxguard/email-deliverability'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/io.inboxguard/email-deliverability

Average score: 58.6 / 100Cloudy
Tools: 28
Near-identical descriptions: 0

Across the server

Minor
28 tools. Above 25, models start to tell tools apart less well.many_tools

Tools

list_alerts

49 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 20 / 25
Return value: 0 / 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
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
Says nothing about what it returns.no_return_info

list_domains

49 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 25 / 25
Return value: 0 / 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
Minor
Says nothing about what it returns.no_return_info

list_inbox_placement_tests

49 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 25 / 25
Return value: 0 / 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
Minor
Says nothing about what it returns.no_return_info

list_scans

49 / 100Cloudy

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

Minor
No `required` list, so every argument is optional.no_required
Minor
Says nothing about what it returns.no_return_info

get_domain

52 / 100Cloudy

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

Minor
Says nothing about what it returns.no_return_info

get_snds_status

52 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 25 / 25
Return value: 0 / 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
Minor
Says nothing about what it returns.no_return_info

get_deliverability_score

54 / 100Cloudy

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

get_portfolio

54 / 100Cloudy

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

Minor
Says nothing about what it returns.no_return_info

get_scan_job

54 / 100Cloudy

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

connect_snds

55 / 100Cloudy

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

Minor
Says nothing about what it returns.no_return_info

get_dmarc_summary

55 / 100Cloudy

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

Minor
Says nothing about what it returns.no_return_info

check_blocklists

57 / 100Cloudy

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

connect_inbox_placement

57 / 100Cloudy

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

Minor
Says nothing about what it returns.no_return_info

get_inbox_placement_status

57 / 100Cloudy

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

Minor
Says nothing about what it returns.no_return_info

list_registrar_connections

57 / 100Cloudy

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

Minor
Says nothing about what it returns.no_return_info

analyze_headers

58 / 100Cloudy

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

remove_domain

58 / 100Cloudy

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

Minor
Says nothing about what it returns.no_return_info

resolve_alert

58 / 100Cloudy

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

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

get_inbox_placement_test

59 / 100Cloudy

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

No issues.

start_inbox_placement_test

59 / 100Cloudy

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

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

scan_domains_batch

60 / 100Cloudy

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

Minor
Says nothing about what it returns.no_return_info

get_snds_ip_stats

64 / 100Cloudy

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

No issues.

create_notification_channel

69 / 100Cloudy

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

No issues.

apply_dns_fix

70 / 100Clear

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

Minor
Says nothing about what it returns.no_return_info

create_share_link

70 / 100Clear

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

No issues.

get_dns_fix_plan

70 / 100Clear

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

No issues.

scan_domain

72 / 100Clear

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

No issues.

get_deliverability_report

75 / 100Clear

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