Forecall
Failure recordsDocs
All scored servers

Harvest MCP by usefulapi: tool descriptions scored io.usefulapi/harvest

tools/list taken
(UTC)
From
Official MCP Registry
Connected to
https://harvest.usefulapi.io/mcp
Homepage
usefulapi.io/harvest/
Repository
github.com/m190/usefulapi-mcp
Scoring rules
v2
Removal
support@forecall.dev
Score this URL as it is today

Scores, issues and names only

This page shows how Harvest MCP by usefulapi (io.usefulapi/harvest)'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.usefulapi/harvest
Average score
47.1 / 100Cloudy
Tools
20
Near-identical descriptions
8

Across the server

Tools whose descriptions are nearly the same

8 of 8 pairs shown, highest description similarity first.
ToolToolDescription similarityName similarity
harvest_list_invoicesharvest_list_estimates0.800.50
harvest_list_projectsharvest_list_clients0.770.50
harvest_list_clientsharvest_list_users0.770.50
harvest_list_time_entriesharvest_list_expenses0.710.40
harvest_list_projectsharvest_list_users0.710.50
harvest_list_invoicesharvest_list_expenses0.670.50
harvest_stop_time_entryharvest_restart_time_entry0.620.60
harvest_list_estimatesharvest_list_expenses0.610.50

Tools

harvest_list_clients

42 / 100Cloudy

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

harvest_list_projects

42 / 100Cloudy

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

harvest_list_users

42 / 100Cloudy

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

harvest_get_client

43 / 100Cloudy

Purpose
13 / 20
When to use
0 / 20
Arguments
23 / 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
  • Minor
    Required identifiers whose description does not say where the value comes from: client_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

harvest_get_project

43 / 100Cloudy

Purpose
13 / 20
When to use
0 / 20
Arguments
23 / 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
  • Minor
    Required identifiers whose description does not say where the value comes from: project_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

harvest_restart_time_entry

44 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
23 / 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
    Its description is nearly the same as harvest_stop_time_entry's (similarity 0.62); only the names and schemas tell them apart. Say in this description when to use harvest_stop_time_entry instead.confusable_pair
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: time_entry_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

harvest_list_expenses

45 / 100Cloudy

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

harvest_list_tasks

45 / 100Cloudy

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

harvest_list_time_entries

45 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
18 / 25
Return value
0 / 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 harvest_list_expenses's (similarity 0.71); only the names and schemas tell them apart. Say in this description when to use harvest_list_expenses instead.confusable_pair
  • 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

harvest_list_estimates

46 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
19 / 25
Return value
0 / 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 harvest_list_invoices's (similarity 0.80); only the names and schemas tell them apart. Say in this description when to use harvest_list_invoices instead.confusable_pair
  • Minor
    Its description is nearly the same as harvest_list_expenses's (similarity 0.61); only the names and schemas tell them apart. Say in this description when to use harvest_list_expenses instead.confusable_pair
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

harvest_list_invoices

46 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
19 / 25
Return value
0 / 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 harvest_list_estimates's (similarity 0.80); only the names and schemas tell them apart. Say in this description when to use harvest_list_estimates instead.confusable_pair
  • Minor
    Its description is nearly the same as harvest_list_expenses's (similarity 0.67); only the names and schemas tell them apart. Say in this description when to use harvest_list_expenses instead.confusable_pair
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

harvest_delete_time_entry

47 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 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
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: time_entry_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

harvest_get_invoice

47 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 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
  • Minor
    Required identifiers whose description does not say where the value comes from: invoice_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

harvest_get_time_entry

47 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 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
  • Minor
    Required identifiers whose description does not say where the value comes from: time_entry_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

harvest_stop_time_entry

47 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 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
    Its description is nearly the same as harvest_restart_time_entry's (similarity 0.62); only the names and schemas tell them apart. Say in this description when to use harvest_restart_time_entry instead.confusable_pair
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: time_entry_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

harvest_update_time_entry

51 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
19 / 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
    String arguments with no constraint or example: notes.loose_string_param
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: time_entry_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

harvest_get_company

52 / 100Cloudy

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

harvest_get_current_user

52 / 100Cloudy

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

harvest_list_project_assignments

55 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
20 / 25
Return value
0 / 15
Constraints and side effects
10 / 10
Examples
0 / 10
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

harvest_create_time_entry

61 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
19 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
10 / 10
  • Minor
    Says nothing about what it returns.no_return_info

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