All scored servers

btw: tool descriptions scored space.btw/btw

tools/list taken
(UTC)
Connected to
https://btw.space/mcp?utm_source=mcp-registry
Homepage
btw.space
Scoring rules
v2
Score this URL as it is today

Scores, issues and names only

This page shows how btw (space.btw/btw)'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/space.btw/btw
Average score
48.8 / 100Cloudy
Tools
19
Near-identical descriptions
2

Across the server

Tools whose descriptions are nearly the same

2 of 2 pairs shown, highest description similarity first.
ToolToolDescription similarityName similarity
holdjoin0.960.00
releaseleave0.880.00

Tools

join_chain

23 / 100Rain

Purpose
6 / 20
When to use
10 / 20
Arguments
0 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description only restates the name (7 words).restates_name
  • Major
    The description is too short (7 words).too_short
  • Major
    Arguments without a description: id, monthly_commit_usd, team_name.param_no_description
  • Minor
    String arguments with no constraint or example: id, team_name.loose_string_param
  • 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

park_intent

27 / 100Rain

Purpose
10 / 20
When to use
10 / 20
Arguments
0 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Arguments without a description: provider, category, min_discount_pct, monthly_cap_usd, note.param_no_description
  • Minor
    String arguments with no constraint or example: provider, category, note.loose_string_param
  • 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

leave

37 / 100Rain

Purpose
17 / 20
When to use
0 / 20
Arguments
13 / 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: email, commitment_id.param_no_description
  • Minor
    Its description is nearly the same as release's (similarity 0.88); only the names and schemas tell them apart. Say in this description when to use release 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: commitment_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

status

39 / 100Rain

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

release

40 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
13 / 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: email, commitment_id.param_no_description
  • Minor
    Its description is nearly the same as leave's (similarity 0.88); only the names and schemas tell them apart. Say in this description when to use leave 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: commitment_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

book_stats

46 / 100Cloudy

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

my_agent

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

list_chains

49 / 100Cloudy

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

get_chain

50 / 100Cloudy

Purpose
10 / 20
When to use
10 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    The description is too short (6 words).too_short
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

park

51 / 100Cloudy

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

want_gym

52 / 100Cloudy

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

want_software

54 / 100Cloudy

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

want_stay

56 / 100Cloudy

Purpose
17 / 20
When to use
5 / 20
Arguments
20 / 25
Return value
7 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    Arguments without a description: note.param_no_description

join

57 / 100Cloudy

Purpose
17 / 20
When to use
5 / 20
Arguments
21 / 25
Return value
7 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    Its description is nearly the same as hold's (similarity 0.96); only the names and schemas tell them apart. Say in this description when to use hold instead.confusable_pair

sync_wishlist

57 / 100Cloudy

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

want_home

59 / 100Cloudy

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

No issues.

hold

60 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
21 / 25
Return value
7 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    Its description is nearly the same as join's (similarity 0.96); only the names and schemas tell them apart. Say in this description when to use join instead.confusable_pair

want

60 / 100Cloudy

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

waitlist

63 / 100Cloudy

Purpose
17 / 20
When to use
15 / 20
Arguments
19 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    No `required` list, so every argument is optional.no_required
  • 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