All scored servers

HeyClaude — Claude & AI workflow directory: tool descriptions scored io.github.JSONbored/heyclaude

tools/list taken
(UTC)
Connected to
https://heyclau.de/api/mcp
Homepage
heyclau.de
Scoring rules
v2
Score this URL as it is today

Scores, issues and names only

This page shows how HeyClaude — Claude & AI workflow directory (io.github.JSONbored/heyclaude)'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.github.JSONbored/heyclaude
Average score
60.1 / 100Cloudy
Tools
28
Near-identical descriptions
1

Across the server

  • Minor
    28 tools. Above 25, models start to tell tools apart less well.many_tools
  • Minor
    The server has no instructions. Say there, once, what the server is for and when to use it: Claude Code and Gemini CLI read the instructions before the tool descriptions.instructions_missing

Tools whose descriptions are nearly the same

1 of 1 pairs shown, highest description similarity first.
ToolToolDescription similarityName similarity
entry.trustentry.safety0.610.33

Tools

submission.validate

42 / 100Cloudy

Purpose
17 / 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: fields.name, fields.title, fields.slug, fields.category, fields.github_url, fields.docs_url, fields.source_url, fields.brand_name, fields.brand_domain, fields.author, fields.contact_email, fields.tags, fields.description, fields.card_description, fields.full_copyable_content, fields.install_command, fields.usage_snippet, fields.command_syntax, fields.trigger, fields.guide_content, fields.items, fields.script_language, fields.skill_type, fields.skill_level, fields.verification_status, fields.verified_at, fields.download_url, fields.config_snippet, fields.retrieval_sources, fields.tested_platforms, fields.prerequisites, fields.safety_notes, fields.privacy_notes, fields.troubleshooting_section, fields.installation_order, fields.estimated_setup_time, fields.difficulty.param_no_description
  • Minor
    String arguments with no constraint or example: fields.safety_notes, fields.privacy_notes.loose_string_param
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description

submission.review

43 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
11 / 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: fields.name, fields.title, fields.slug, fields.category, fields.github_url, fields.docs_url, fields.source_url, fields.brand_name, fields.brand_domain, fields.author, fields.contact_email, fields.tags, fields.description, fields.card_description, fields.full_copyable_content, fields.install_command, fields.usage_snippet, fields.command_syntax, fields.trigger, fields.guide_content, fields.items, fields.script_language, fields.skill_type, fields.skill_level, fields.verification_status, fields.verified_at, fields.download_url, fields.config_snippet, fields.retrieval_sources, fields.tested_platforms, fields.prerequisites, fields.safety_notes, fields.privacy_notes, fields.troubleshooting_section, fields.installation_order, fields.estimated_setup_time, fields.difficulty.param_no_description
  • Minor
    String arguments with no constraint or example: fields.safety_notes, fields.privacy_notes.loose_string_param
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description

submission.urls

43 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
11 / 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: fields.name, fields.title, fields.slug, fields.category, fields.github_url, fields.docs_url, fields.source_url, fields.brand_name, fields.brand_domain, fields.author, fields.contact_email, fields.tags, fields.description, fields.card_description, fields.full_copyable_content, fields.install_command, fields.usage_snippet, fields.command_syntax, fields.trigger, fields.guide_content, fields.items, fields.script_language, fields.skill_type, fields.skill_level, fields.verification_status, fields.verified_at, fields.download_url, fields.config_snippet, fields.retrieval_sources, fields.tested_platforms, fields.prerequisites, fields.safety_notes, fields.privacy_notes, fields.troubleshooting_section, fields.installation_order, fields.estimated_setup_time, fields.difficulty.param_no_description
  • Minor
    String arguments with no constraint or example: fields.safety_notes, fields.privacy_notes.loose_string_param
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description

submission.prepare

45 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
10 / 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: fields.name, fields.title, fields.slug, fields.category, fields.github_url, fields.docs_url, fields.source_url, fields.brand_name, fields.brand_domain, fields.author, fields.contact_email, fields.tags, fields.description, fields.card_description, fields.full_copyable_content, fields.install_command, fields.usage_snippet, fields.command_syntax, fields.trigger, fields.guide_content, fields.items, fields.script_language, fields.skill_type, fields.skill_level, fields.verification_status, fields.verified_at, fields.download_url, fields.config_snippet, fields.retrieval_sources, fields.tested_platforms, fields.prerequisites, fields.safety_notes, fields.privacy_notes, fields.troubleshooting_section, fields.installation_order, fields.estimated_setup_time, fields.difficulty.param_no_description
  • Minor
    String arguments with no constraint or example: fields.safety_notes, fields.privacy_notes.loose_string_param
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description

entry.coverage

49 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
14 / 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: entries[].category, entries[].slug, platform.param_no_description

submission.guidance

50 / 100Cloudy

Purpose
13 / 20
When to use
0 / 20
Arguments
22 / 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
  • Minor
    No `required` list, so every argument is optional.no_required

install.compatibility

51 / 100Cloudy

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

submission.schema

53 / 100Cloudy

Purpose
13 / 20
When to use
0 / 20
Arguments
22 / 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
  • Minor
    No `required` list, so every argument is optional.no_required

registry.updates

55 / 100Cloudy

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

registry.info

56 / 100Cloudy

Purpose
13 / 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

submission.duplicates

59 / 100Cloudy

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

entry.safety

60 / 100Cloudy

Purpose
20 / 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
  • Minor
    Its description is nearly the same as entry.trust's (similarity 0.61); only the names and schemas tell them apart. Say in this description when to use entry.trust instead.confusable_pair

registry.feeds

60 / 100Cloudy

Purpose
17 / 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

registry.stats

60 / 100Cloudy

Purpose
17 / 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

submission.policy

60 / 100Cloudy

Purpose
17 / 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

install.setup

62 / 100Cloudy

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

registry.list

62 / 100Cloudy

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

registry.search

62 / 100Cloudy

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

entry.compare

65 / 100Cloudy

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

entry.related

65 / 100Cloudy

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

entry.trust

65 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
25 / 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
  • Minor
    Its description is nearly the same as entry.safety's (similarity 0.61); only the names and schemas tell them apart. Say in this description when to use entry.safety instead.confusable_pair

install.adapter

65 / 100Cloudy

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

install.guidance

65 / 100Cloudy

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

submission.examples

67 / 100Cloudy

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

registry.plan

68 / 100Cloudy

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

entry.detail

73 / 100Clear

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

registry.recommend

87 / 100Clear

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

No issues.

entry.asset

92 / 100Clear

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