All scored servers

FreightFA: tool descriptions scored com.freightfa.mcp/freightfa

tools/list taken
(UTC)
Connected to
https://mcp.freightfa.com/mcp
Scoring rules
v2
Score this URL as it is today

Scores, issues and names only

This page shows how FreightFA (com.freightfa.mcp/freightfa)'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/com.freightfa.mcp/freightfa
Average score
56.6 / 100Cloudy
Tools
27
Near-identical descriptions
1

Across the server

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

Tools whose descriptions are nearly the same

1 of 1 pairs shown, highest description similarity first.
ToolToolDescription similarityName similarity
estimate_truckload_rateestimate_ltl_rate0.670.50

Tools

list_rate_alerts

36 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (8 words).restates_name
  • 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_freight_index_outlook

44 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
20 / 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
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

get_rail_market_outlook

44 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
20 / 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
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

get_rfp

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: rfp_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

find_intermodal_hubs

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
    Says nothing about what it returns.no_return_info

get_market_outlook

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
    Says nothing about what it returns.no_return_info

ask_freight_analyst

50 / 100Cloudy

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

list_recent_searches

50 / 100Cloudy

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

lookup_carrier

50 / 100Cloudy

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

draft_pushback_email

52 / 100Cloudy

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

estimate_truckload_rate

52 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
13 / 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
  • Minor
    Its description is nearly the same as estimate_ltl_rate's (similarity 0.67); only the names and schemas tell them apart. Say in this description when to use estimate_ltl_rate instead.confusable_pair
  • Minor
    Arguments without a description: destination, origin_zip, destination_zip.param_no_description
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description

list_rfps

52 / 100Cloudy

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

create_rate_alert

55 / 100Cloudy

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

explain_freight_term

56 / 100Cloudy

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

get_barge_outlook

57 / 100Cloudy

Purpose
17 / 20
When to use
5 / 20
Arguments
23 / 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_market_snapshot

59 / 100Cloudy

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

calculate_margin

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

estimate_intermodal_rate

60 / 100Cloudy

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

create_rfp

62 / 100Cloudy

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

estimate_barge_rate

62 / 100Cloudy

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

No issues.

estimate_ltl_rate

62 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
23 / 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
  • Minor
    Its description is nearly the same as estimate_truckload_rate's (similarity 0.67); only the names and schemas tell them apart. Say in this description when to use estimate_truckload_rate instead.confusable_pair
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description

estimate_network_cost

63 / 100Cloudy

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

get_freight_news

66 / 100Cloudy

Purpose
17 / 20
When to use
5 / 20
Arguments
20 / 25
Return value
7 / 15
Constraints and side effects
7 / 10
Examples
10 / 10
  • Minor
    No `required` list, so every argument is optional.no_required

get_freight_brief

67 / 100Cloudy

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

estimate_rail_rate

72 / 100Clear

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

No issues.

recommend_mode

75 / 100Clear

Purpose
20 / 20
When to use
15 / 20
Arguments
21 / 25
Return value
7 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description

check_freight_bill

77 / 100Clear

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