All scored servers

livedot MCP: tool descriptions scored me.livedot/mcp

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

Scores, issues and names only

This page shows how livedot MCP (me.livedot/mcp)'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/me.livedot/mcp
Average score
74.0 / 100Clear
Tools
20
Near-identical descriptions
0

Across the server

No server-wide issues.

Tools

where_is

55 / 100Cloudy

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

update_event

58 / 100Cloudy

Purpose
17 / 20
When to use
5 / 20
Arguments
16 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    Arguments without a description: days[].day, days[].date, days[].time.param_no_description
  • Minor
    String arguments with no constraint or example: event_id, name, days[].date, days[].time.loose_string_param
  • Minor
    Required identifiers whose description does not say where the value comes from: event_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

add_tour_notes

62 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
22 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    Required identifiers whose description does not say where the value comes from: event_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

list_my_events

62 / 100Cloudy

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

publish_event

65 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
20 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    Required identifiers whose description does not say where the value comes from: event_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

fly_route

71 / 100Clear

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

invite_members

72 / 100Clear

Purpose
20 / 20
When to use
0 / 20
Arguments
17 / 25
Return value
15 / 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
    String arguments with no constraint or example: people[].name, people[].email.loose_string_param
  • Minor
    No `required` list, so every argument is optional.no_required

tour_notes

72 / 100Clear

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

No issues.

find_events

73 / 100Clear

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

No issues.

post_club_ride

73 / 100Clear

Purpose
20 / 20
When to use
10 / 20
Arguments
18 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
10 / 10
  • Minor
    Arguments without a description: weekly.days, weekly.time.param_no_description
  • Minor
    String arguments with no constraint or example: weekly.time.loose_string_param

event_weather

74 / 100Clear

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

No issues.

plan_route

77 / 100Clear

Purpose
17 / 20
When to use
15 / 20
Arguments
20 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
10 / 10
  • Minor
    String arguments with no constraint or example: files[].gpx.loose_string_param

create_event

78 / 100Clear

Purpose
20 / 20
When to use
10 / 20
Arguments
16 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
10 / 10
  • Minor
    Arguments without a description: weekly.days, weekly.time.param_no_description
  • Minor
    String arguments with no constraint or example: files[].gpx, weekly.time.loose_string_param
  • Minor
    No `required` list, so every argument is optional.no_required

find_coaches

79 / 100Clear

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

No issues.

event_status

83 / 100Clear

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

No issues.

find_clubs

83 / 100Clear

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

No issues.

club_in_race

85 / 100Clear

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

tap_on_the_back

85 / 100Clear

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

tour_route

86 / 100Clear

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

No issues.

find_person

88 / 100Clear

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