All scored servers

Evenium MCP by usefulapi: tool descriptions scored io.usefulapi/evenium

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

Scores, issues and names only

This page shows how Evenium MCP by usefulapi (io.usefulapi/evenium)'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.usefulapi/evenium
Average score
52.1 / 100Cloudy
Tools
19
Near-identical descriptions
3

Across the server

Tools whose descriptions are nearly the same

3 of 3 pairs shown, highest description similarity first.
ToolToolDescription similarityName similarity
evenium_get_guest_post_statusevenium_update_guest_post_status0.620.67
evenium_get_guest_statusevenium_get_guest_post_status0.450.80
evenium_get_eventevenium_get_event_part0.360.75

Tools

evenium_create_contact

45 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
13 / 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
  • Major
    Arguments without a description: first_name, last_name, email, gender, company, fields[].value.param_no_description
  • Minor
    Says nothing about what it returns.no_return_info

evenium_create_guest

46 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
14 / 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
  • Major
    Arguments without a description: first_name, last_name, email, gender, company.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: event_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

evenium_update_contact

48 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
16 / 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: email, company, fields[].value.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: contact_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

evenium_get_event

49 / 100Cloudy

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

evenium_get_event_part

49 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
23 / 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
    Its description is nearly the same as evenium_get_event's (similarity 0.36); only the names and schemas tell them apart. Say in this description when to use evenium_get_event 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: event_id, event_part_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

evenium_get_contact_events

52 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 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
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: contact_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

evenium_get_guest

52 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 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
    Says nothing about what it returns.no_return_info
  • 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

evenium_get_guest_accommodations

52 / 100Cloudy

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

evenium_list_contacts

52 / 100Cloudy

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

evenium_list_event_part_registrations

52 / 100Cloudy

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

evenium_list_events

52 / 100Cloudy

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

evenium_list_hotels

52 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 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
    Says nothing about what it returns.no_return_info
  • 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

evenium_get_contact

54 / 100Cloudy

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

evenium_get_guest_post_status

54 / 100Cloudy

Purpose
14 / 20
When to use
5 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    Its description is nearly the same as evenium_update_guest_post_status's (similarity 0.62); only the names and schemas tell them apart. Say in this description when to use evenium_update_guest_post_status instead.confusable_pair
  • Minor
    Its description is nearly the same as evenium_get_guest_status's (similarity 0.45); only the names and schemas tell them apart. Say in this description when to use evenium_get_guest_status 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: event_id, contact_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

evenium_get_guest_status

54 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 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
    Its description is nearly the same as evenium_get_guest_post_status's (similarity 0.45); only the names and schemas tell them apart. Say in this description when to use evenium_get_guest_post_status 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: event_id, contact_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

evenium_list_event_parts

55 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
23 / 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
    Says nothing about what it returns.no_return_info
  • 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

evenium_update_guest_status

55 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
18 / 25
Return value
0 / 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: status.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: event_id, contact_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

evenium_update_guest_post_status

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
    Its description is nearly the same as evenium_get_guest_post_status's (similarity 0.62); only the names and schemas tell them apart. Say in this description when to use evenium_get_guest_post_status instead.confusable_pair
  • Minor
    Arguments without a description: post_status.param_no_description
  • 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
  • Minor
    Required identifiers whose description does not say where the value comes from: event_id, contact_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

evenium_list_guests

60 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 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
    Says nothing about what it returns.no_return_info
  • 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

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