All scored servers

welance/directory: tool descriptions scored com.welance/directory

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

Scores, issues and names only

This page shows how welance/directory (com.welance/directory)'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.welance/directory
Average score
46.5 / 100Cloudy
Tools
20
Near-identical descriptions
1

Across the server

Tools whose descriptions are nearly the same

1 of 1 pairs shown, highest description similarity first.
ToolToolDescription similarityName similarity
propose_bookingpropose_booking_accept0.350.67

Tools

list_open_briefs

31 / 100Rain

Purpose
17 / 20
When to use
0 / 20
Arguments
7 / 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: status, tangible.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The meaning of the boolean argument tangible is unclear.vague_boolean
  • Minor
    Says nothing about what it returns.no_return_info

read_booking

31 / 100Rain

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

read_brief

31 / 100Rain

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

read_invoices

42 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
10 / 25
Return value
0 / 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
  • Major
    Arguments without a description: identity, identities, from, to, limit.param_no_description
  • Minor
    Says nothing about what it returns.no_return_info

match_brief

44 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
15 / 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
    Arguments without a description: title.param_no_description
  • Minor
    String arguments with no constraint or example: title.loose_string_param
  • Minor
    Says nothing about what it returns.no_return_info

propose_team_invite

44 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
13 / 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
  • Major
    Arguments without a description: teamKey, name, email, role.param_no_description

propose_brief_draft

45 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
14 / 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
  • Major
    Arguments without a description: title, markdown, answers.param_no_description

propose_brief_publish

45 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
14 / 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
  • Major
    Arguments without a description: title, markdown, language.param_no_description

read_profile

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

propose_booking

48 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
14 / 25
Return value
7 / 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: appId, slots, note.param_no_description
  • Minor
    Its description is nearly the same as propose_booking_accept's (similarity 0.35); only the names and schemas tell them apart. Say in this description when to use propose_booking_accept instead.confusable_pair
  • Minor
    Required identifiers whose description does not say where the value comes from: appId. Name the tool or the place that returns it, or models look it up first.id_source_missing

brief_rules

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

directory_capabilities

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

propose_booking_accept

49 / 100Cloudy

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

propose_pitch_draft

49 / 100Cloudy

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

propose_pitch_send

49 / 100Cloudy

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

read_my_pitches

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

read_pitchable_briefs

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

preview_teams

59 / 100Cloudy

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

read_my_teams

59 / 100Cloudy

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

propose_profile_update

61 / 100Cloudy

Purpose
17 / 20
When to use
10 / 20
Arguments
15 / 25
Return value
7 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    Arguments without a description: entity, teamKey, memberKey, organisationId, changes, changes[].field, changes[].attachmentId, removeSkills, removeShipped, addLangs, removeLangs.param_no_description

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