dev.dnsdoctor/dns-doctor: tool descriptions scored

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

Scores, issues and names only

This page shows how dev.dnsdoctor/dns-doctor'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/dev.dnsdoctor/dns-doctor

Average score: 84.5 / 100Clear
Tools: 27
Near-identical descriptions: 0

Across the server

Minor
27 tools. Above 25, models start to tell tools apart less well.many_tools
Minor
The server's instructions are 7587 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

parse_dmarc_report

68 / 100Cloudy

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

No issues.

list_my_domains

75 / 100Clear

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

No issues.

check_bimi

76 / 100Clear

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

No issues.

validate_dmarc_record

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.

check_lookalikes

80 / 100Clear

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

No issues.

check_reverse_dns

80 / 100Clear

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

No issues.

get_readiness

80 / 100Clear

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

No issues.

start_email_test

80 / 100Clear

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

No issues.

get_domain_records

81 / 100Clear

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

No issues.

lookup_registration

81 / 100Clear

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

No issues.

generate_dmarc_record

83 / 100Clear

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

No issues.

build_dmarc_upgrade

85 / 100Clear

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

No issues.

check_dkim_selector

85 / 100Clear

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

No issues.

check_record

85 / 100Clear

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

No issues.

list_email_tests

85 / 100Clear

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

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

get_lookalikes

87 / 100Clear

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

No issues.

audit_spf_includes

88 / 100Clear

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

No issues.

get_alerts

88 / 100Clear

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

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

start_monitoring_signup

88 / 100Clear

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

No issues.

add_monitored_domain

90 / 100Clear

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

No issues.

build_parked_domain_records

90 / 100Clear

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

No issues.

check_domain_verification

90 / 100Clear

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

No issues.

count_spf_lookups

90 / 100Clear

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

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

get_report

90 / 100Clear

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

No issues.

check_propagation

92 / 100Clear

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

No issues.

get_email_test

93 / 100Clear

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

No issues.

scan_domain

93 / 100Clear

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