All scored servers

Sonar Connections: tool descriptions scored com.sonarconnections/sonar-connections

tools/list taken
(UTC)
Connected to
https://mcpconnector-gtlizqtvza-uw.a.run.app/public
Scoring rules
v2
Score this URL as it is today

Scores, issues and names only

This page shows how Sonar Connections (com.sonarconnections/sonar-connections)'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.sonarconnections/sonar-connections
Average score
67.3 / 100Cloudy
Tools
55
Near-identical descriptions
9

Across the server

  • Major
    55 tools. Above 40, models choose less accurately.too_many_tools
  • Minor
    The server's instructions are 2556 characters. Claude Code reads only the first 2,048 by default (Codex 0.154.0 reads them whole). Put what the server is for first.instructions_long

Tools whose descriptions are nearly the same

9 of 9 pairs shown, highest description similarity first.
ToolToolDescription similarityName similarity
event_session_renameevent_session_cancel0.890.50
event_session_moveevent_session_rename0.860.50
event_pass_reissueevent_pass_revoke0.800.50
event_session_moveevent_session_cancel0.790.50
booth_enter_rafflebooth_claim_swag0.750.20
booth_enter_rafflebooth_take_invite0.750.20
booth_claim_swagbooth_take_invite0.700.20
event_session_renameevent_session_add0.610.50
site_publishsite_undo_publish0.570.67

Tools

event_find_matches

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
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

event_text_alerts

52 / 100Cloudy

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

events_offers

52 / 100Cloudy

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

biz_set_item_availability

54 / 100Cloudy

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

biz_storefront

54 / 100Cloudy

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

booth_set_away

54 / 100Cloudy

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

biz_order_status

55 / 100Cloudy

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

biz_order

57 / 100Cloudy

Purpose
17 / 20
When to use
5 / 20
Arguments
18 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
10 / 10
  • Minor
    String arguments with no constraint or example: firstName.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: pickupWindowId. Name the tool or the place that returns it, or models look it up first.id_source_missing

event_card_links

57 / 100Cloudy

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

event_meetup_rsvp

60 / 100Cloudy

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

site_list

60 / 100Cloudy

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

No issues.

event_pass_notice

61 / 100Cloudy

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

biz_menu

62 / 100Cloudy

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

booth_connect

62 / 100Cloudy

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

event_pass_reissue

62 / 100Cloudy

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

event_pass_revoke

62 / 100Cloudy

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

event_wallet_pass

62 / 100Cloudy

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

event_organizer_overview

63 / 100Cloudy

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

No issues.

site_get

63 / 100Cloudy

Purpose
17 / 20
When to use
5 / 20
Arguments
21 / 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: siteId. Name the tool or the place that returns it, or models look it up first.id_source_missing

biz_availability

64 / 100Cloudy

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

event_accept

64 / 100Cloudy

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

event_inbox

64 / 100Cloudy

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

event_reply

64 / 100Cloudy

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

No issues.

events_booths

65 / 100Cloudy

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

No issues.

event_guest_request_handled

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
    Required identifiers whose description does not say where the value comes from: requestId. Name the tool or the place that returns it, or models look it up first.id_source_missing

event_set_intent

66 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
17 / 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
    Arguments without a description: facets.confirm, facets.add, facets.remove.param_no_description
  • Minor
    String arguments with no constraint or example: eventId.loose_string_param
  • Minor
    The meaning of the boolean argument facets.confirm is unclear.vague_boolean

biz_info

67 / 100Cloudy

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

booth_claim_swag

67 / 100Cloudy

Purpose
17 / 20
When to use
5 / 20
Arguments
18 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    Its description is nearly the same as booth_enter_raffle's (similarity 0.75); only the names and schemas tell them apart. Say in this description when to use booth_enter_raffle instead.confusable_pair
  • Minor
    Its description is nearly the same as booth_take_invite's (similarity 0.70); only the names and schemas tell them apart. Say in this description when to use booth_take_invite instead.confusable_pair
  • Minor
    Required identifiers whose description does not say where the value comes from: eventId, boothId. Name the tool or the place that returns it, or models look it up first.id_source_missing

booth_enter_raffle

67 / 100Cloudy

Purpose
17 / 20
When to use
5 / 20
Arguments
18 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    Its description is nearly the same as booth_claim_swag's (similarity 0.75); only the names and schemas tell them apart. Say in this description when to use booth_claim_swag instead.confusable_pair
  • Minor
    Its description is nearly the same as booth_take_invite's (similarity 0.75); only the names and schemas tell them apart. Say in this description when to use booth_take_invite instead.confusable_pair
  • Minor
    Required identifiers whose description does not say where the value comes from: eventId, boothId. Name the tool or the place that returns it, or models look it up first.id_source_missing

booth_take_invite

67 / 100Cloudy

Purpose
17 / 20
When to use
5 / 20
Arguments
18 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    Its description is nearly the same as booth_enter_raffle's (similarity 0.75); only the names and schemas tell them apart. Say in this description when to use booth_enter_raffle instead.confusable_pair
  • Minor
    Its description is nearly the same as booth_claim_swag's (similarity 0.70); only the names and schemas tell them apart. Say in this description when to use booth_claim_swag instead.confusable_pair
  • Minor
    Required identifiers whose description does not say where the value comes from: eventId, boothId. Name the tool or the place that returns it, or models look it up first.id_source_missing

event_meetup_announce

67 / 100Cloudy

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

event_redeem_code

67 / 100Cloudy

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

event_requests

67 / 100Cloudy

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

No issues.

event_send_request

68 / 100Cloudy

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

site_create

68 / 100Cloudy

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

No issues.

event_card_save_linkedin

69 / 100Cloudy

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

No issues.

event_change_undo

69 / 100Cloudy

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

No issues.

event_guest_requests

69 / 100Cloudy

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

No issues.

events_list

70 / 100Clear

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

No issues.

site_publish

73 / 100Clear

Purpose
17 / 20
When to use
15 / 20
Arguments
21 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    Its description is nearly the same as site_undo_publish's (similarity 0.57); only the names and schemas tell them apart. Say in this description when to use site_undo_publish instead.confusable_pair
  • Minor
    Required identifiers whose description does not say where the value comes from: siteId. Name the tool or the place that returns it, or models look it up first.id_source_missing

site_undo_publish

73 / 100Clear

Purpose
17 / 20
When to use
15 / 20
Arguments
21 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    Its description is nearly the same as site_publish's (similarity 0.57); only the names and schemas tell them apart. Say in this description when to use site_publish instead.confusable_pair
  • Minor
    Required identifiers whose description does not say where the value comes from: siteId. Name the tool or the place that returns it, or models look it up first.id_source_missing

ui_card_diag

74 / 100Clear

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

No issues.

events_speakers

75 / 100Clear

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

No issues.

events_whats_on

75 / 100Clear

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

No issues.

site_edit

75 / 100Clear

Purpose
17 / 20
When to use
20 / 20
Arguments
13 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
10 / 10
  • Major
    Arguments without a description: ops[].page, ops[].kind, ops[].before, ops[].after, ops[].into, ops[].rightOf, ops[].leftOf, ops[].columns, ops[].index, ops[].toPage, ops[].field, ops[].props, ops[].title, ops[].navLabel, ops[].nav, ops[].nav[].label, ops[].nav[].href, ops[].style, ops[].theme.param_no_description
  • Minor
    The description is long (499 words). It helps selection but costs steps and tokens.too_long

event_change_detail

76 / 100Clear

Purpose
17 / 20
When to use
20 / 20
Arguments
22 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
10 / 10
  • Minor
    The description is long (683 words). It helps selection but costs steps and tokens.too_long
  • Minor
    Says nothing about what it returns.no_return_info

event_say_hello

80 / 100Clear

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

No issues.

events_floor_card

82 / 100Clear

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

No issues.

events_get

82 / 100Clear

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

No issues.

events_overview

82 / 100Clear

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

No issues.

events_personal_card

82 / 100Clear

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

No issues.

event_session_add

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
  • Minor
    Its description is nearly the same as event_session_rename's (similarity 0.61); only the names and schemas tell them apart. Say in this description when to use event_session_rename instead.confusable_pair

event_session_cancel

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
  • Minor
    Its description is nearly the same as event_session_rename's (similarity 0.89); only the names and schemas tell them apart. Say in this description when to use event_session_rename instead.confusable_pair
  • Minor
    Its description is nearly the same as event_session_move's (similarity 0.79); only the names and schemas tell them apart. Say in this description when to use event_session_move instead.confusable_pair

event_session_move

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
  • Minor
    Its description is nearly the same as event_session_rename's (similarity 0.86); only the names and schemas tell them apart. Say in this description when to use event_session_rename instead.confusable_pair
  • Minor
    Its description is nearly the same as event_session_cancel's (similarity 0.79); only the names and schemas tell them apart. Say in this description when to use event_session_cancel instead.confusable_pair

event_session_rename

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
  • Minor
    Its description is nearly the same as event_session_cancel's (similarity 0.89); only the names and schemas tell them apart. Say in this description when to use event_session_cancel instead.confusable_pair
  • Minor
    Its description is nearly the same as event_session_move's (similarity 0.86); only the names and schemas tell them apart. Say in this description when to use event_session_move instead.confusable_pair
  • Minor
    Its description is nearly the same as event_session_add's (similarity 0.61); only the names and schemas tell them apart. Say in this description when to use event_session_add instead.confusable_pair

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