All scored servers

Soundcheck Live Event Quotes: tool descriptions scored io.soundchecklive/live-event-quotes

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

Scores, issues and names only

This page shows how Soundcheck Live Event Quotes (io.soundchecklive/live-event-quotes)'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/io.soundchecklive/live-event-quotes
Average score
71.1 / 100Clear
Tools
18
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
request_bookingrequest_sponsorship0.720.33

Tools

get_public_org

59 / 100Cloudy

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

list_positions

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

list_quote_packages

64 / 100Cloudy

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

request_sponsorship

65 / 100Cloudy

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

send_feedback

65 / 100Cloudy

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

No issues.

search_inventory

69 / 100Cloudy

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

read_event_details

70 / 100Clear

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

request_booking

70 / 100Clear

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

search_places

70 / 100Clear

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

get_business

72 / 100Clear

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

get_import_format

72 / 100Clear

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

get_place

74 / 100Clear

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

normalize_inventory

74 / 100Clear

Purpose
20 / 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
    No `required` list, so every argument is optional.no_required

search_businesses

74 / 100Clear

Purpose
20 / 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
    No `required` list, so every argument is optional.no_required

check_import_file

77 / 100Clear

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

No issues.

normalize_positions

77 / 100Clear

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

quote_event

77 / 100Clear

Purpose
17 / 20
When to use
5 / 20
Arguments
20 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
10 / 10
  • Minor
    Arguments without a description: date_range.start, date_range.end.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required

lookup_market_pricing

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