HODDS: tool descriptions scored ai.hodds/hodds

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

Scores, issues and names only

This page shows how HODDS (ai.hodds/hodds)'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/ai.hodds/hodds

Average score: 66.6 / 100Cloudy
Tools: 21
Near-identical descriptions: 1

Across the server

Tools whose descriptions are nearly the same

1 of 1 pairs shown, highest description similarity first.
Tool	Tool	Description similarity	Name similarity
cancel_creator_plan	cancel_plan	0.42	0.67

Tools

read_choice

35 / 100Rain

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 11 / 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
Major
Arguments without a description: operation, input, representation, resume, resume.evaluated_at, resume.dataset_id, resume.snapshot_id, resume.request_id, reference, reference.view, reference.view.result_id, reference.view.field, reference.view.offset.param_no_description
Minor
Says nothing about what it returns.no_return_info

watch_choice

45 / 100Cloudy

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

Major
Arguments without a description: operation, watch_id, request, expected_revision, reset_baseline, after, limit, operation, watch_id, request, expected_revision, reset_baseline, operation, watch_id, operation, watch_id, after, limit.param_no_description
Minor
String arguments with no constraint or example: operation, operation, operation.loose_string_param
Minor
The meaning of the boolean argument reset_baseline is unclear.vague_boolean
Minor
The meaning of the boolean argument reset_baseline is unclear.vague_boolean
Minor
Says nothing about what it returns.no_return_info
Minor
Required identifiers whose description does not say where the value comes from: watch_id, watch_id, watch_id, watch_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

find_comparable_solutions

55 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 10 / 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
Major
Arguments without a description: reference_id, priority, criteria, requirements, context, cost_scenario, locale, limit, view.param_no_description

set_creator_processes

57 / 100Cloudy

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

Major
Arguments without a description: processes.param_no_description

list_watches

64 / 100Cloudy

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

compare_solutions

65 / 100Cloudy

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

Major
Arguments without a description: solution_ids, priority, priority_required, criteria, requirements, context, cost_scenario, locale, view.param_no_description
Minor
The meaning of the boolean argument priority_required is unclear.vague_boolean
Minor
Required identifiers whose description does not say where the value comes from: solution_ids. Name the tool or the place that returns it, or models look it up first.id_source_missing

ack_alerts

67 / 100Cloudy

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

cancel_creator_plan

67 / 100Cloudy

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

cancel_plan

67 / 100Cloudy

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

get_creator_plan

67 / 100Cloudy

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

list_gaps

67 / 100Cloudy

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

set_current_choice

67 / 100Cloudy

Purpose: 17 / 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
Minor
The description mentions none of its 3 or more arguments.params_not_in_description

get_solution

72 / 100Clear

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

get_watch

72 / 100Clear

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

No issues.

list_processes

72 / 100Clear

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

rate_alert

72 / 100Clear

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

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

unwatch_need

72 / 100Clear

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

No issues.

watch_need

72 / 100Clear

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

Minor
Arguments without a description: target, target.kind, target.solution_id, target.capability_ids, context, delivery.param_no_description
Minor
No `required` list, so every argument is optional.no_required

send_feedback

74 / 100Clear

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

No issues.

get_plan

77 / 100Clear

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

No issues.

search_solutions

92 / 100Clear

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