Forecall
Failure recordsDocs
All scored servers

Synchroteam MCP by usefulapi: tool descriptions scored io.usefulapi/synchroteam

tools/list taken
(UTC)
From
Official MCP Registry
Connected to
https://synchroteam.usefulapi.io/mcp
Homepage
usefulapi.io/synchroteam/
Repository
github.com/m190/usefulapi-mcp
Scoring rules
v2
Removal
support@forecall.dev
Score this URL as it is today

Scores, issues and names only

This page shows how Synchroteam MCP by usefulapi (io.usefulapi/synchroteam)'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/synchroteam
Average score
45.1 / 100Cloudy
Tools
33
Near-identical descriptions
4

Across the server

  • Minor
    33 tools. Above 25, models start to tell tools apart less well.many_tools

Tools whose descriptions are nearly the same

4 of 4 pairs shown, highest description similarity first.
ToolToolDescription similarityName similarity
synchroteam_get_customersynchroteam_get_site0.860.50
synchroteam_get_invoicesynchroteam_get_quotation0.780.50
synchroteam_create_customersynchroteam_create_site0.680.50
synchroteam_list_sitessynchroteam_list_equipment0.670.50

Tools

synchroteam_list_projects

33 / 100Rain

Purpose
17 / 20
When to use
0 / 20
Arguments
9 / 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: customer_id, customer_my_id, site_id, site_my_id, equipment_id, equipment_my_id, type_id, type_name.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • 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

synchroteam_list_part_requests

34 / 100Rain

Purpose
17 / 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
  • Minor
    Arguments without a description: is_urgent, is_sent, is_complete, is_deleted.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    The meaning of the boolean argument is_urgent is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument is_sent is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument is_complete is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument is_deleted is unclear.vague_boolean
  • Minor
    Says nothing about what it returns.no_return_info

synchroteam_list_parts

35 / 100Rain

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

synchroteam_list_equipment

36 / 100Rain

Purpose
17 / 20
When to use
0 / 20
Arguments
12 / 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
    Its description is nearly the same as synchroteam_list_sites's (similarity 0.67); only the names and schemas tell them apart. Say in this description when to use synchroteam_list_sites instead.confusable_pair
  • Minor
    Arguments without a description: customer_id, customer_my_id, site_id, site_my_id, sort.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

synchroteam_list_invoices

36 / 100Rain

Purpose
17 / 20
When to use
0 / 20
Arguments
9 / 25
Return value
0 / 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: status, customer_id, customer_my_id, site_id, site_my_id, job_id, job_my_id, job_num.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

synchroteam_list_teams

36 / 100Rain

Purpose
13 / 20
When to use
0 / 20
Arguments
16 / 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
    Arguments without a description: show.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • 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

synchroteam_list_contracts

37 / 100Rain

Purpose
17 / 20
When to use
0 / 20
Arguments
13 / 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
    Arguments without a description: name, customer_id, customer_my_id, site_id, site_my_id, sort.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

synchroteam_list_quotations

37 / 100Rain

Purpose
17 / 20
When to use
0 / 20
Arguments
10 / 25
Return value
0 / 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: status, customer_id, customer_my_id, site_id, site_my_id, job_id, job_my_id, job_num.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

synchroteam_list_depots

40 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
16 / 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
    Arguments without a description: is_default, sort.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    The meaning of the boolean argument is_default is unclear.vague_boolean
  • Minor
    Says nothing about what it returns.no_return_info

synchroteam_get_user

41 / 100Cloudy

Purpose
6 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    The description only restates the name (9 words).restates_name
  • 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

synchroteam_list_jobs

41 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
14 / 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
    Arguments without a description: customer_id, customer_my_id, site_id, site_my_id, equipment_id, equipment_my_id, sort.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

synchroteam_list_sites

41 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
17 / 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
    Its description is nearly the same as synchroteam_list_equipment's (similarity 0.67); only the names and schemas tell them apart. Say in this description when to use synchroteam_list_equipment instead.confusable_pair
  • Minor
    Arguments without a description: sort.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

synchroteam_get_depot

44 / 100Cloudy

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

synchroteam_get_part

45 / 100Cloudy

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

synchroteam_create_customer

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: contact_first_name, contact_last_name, contact_email, contact_phone, contact_fax, vat_number.param_no_description
  • Minor
    Its description is nearly the same as synchroteam_create_site's (similarity 0.68); only the names and schemas tell them apart. Say in this description when to use synchroteam_create_site instead.confusable_pair
  • Minor
    Says nothing about what it returns.no_return_info

synchroteam_list_activities

46 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
12 / 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: activity_type_category, user_id, user_login, team_id, sort.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required

synchroteam_list_customers

48 / 100Cloudy

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

synchroteam_complete_job

49 / 100Cloudy

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

synchroteam_get_customer

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 synchroteam_get_site's (similarity 0.86); only the names and schemas tell them apart. Say in this description when to use synchroteam_get_site instead.confusable_pair
  • Minor
    Says nothing about what it returns.no_return_info

synchroteam_get_equipment

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
    Says nothing about what it returns.no_return_info

synchroteam_get_invoice

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 synchroteam_get_quotation's (similarity 0.78); only the names and schemas tell them apart. Say in this description when to use synchroteam_get_quotation instead.confusable_pair
  • Minor
    Says nothing about what it returns.no_return_info

synchroteam_get_site

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 synchroteam_get_customer's (similarity 0.86); only the names and schemas tell them apart. Say in this description when to use synchroteam_get_customer instead.confusable_pair
  • Minor
    Says nothing about what it returns.no_return_info

synchroteam_list_job_types

49 / 100Cloudy

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

synchroteam_list_users

49 / 100Cloudy

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

synchroteam_update_customer

49 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
12 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    Arguments without a description: name, contact_first_name, contact_last_name, contact_email, contact_phone, contact_fax, vat_number.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: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

synchroteam_create_equipment

50 / 100Cloudy

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

synchroteam_create_site

50 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
18 / 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 synchroteam_create_customer's (similarity 0.68); only the names and schemas tell them apart. Say in this description when to use synchroteam_create_customer instead.confusable_pair
  • Minor
    Arguments without a description: contact_name, contact_email, contact_phone, contact_mobile.param_no_description
  • Minor
    Says nothing about what it returns.no_return_info

synchroteam_get_job

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

synchroteam_get_quotation

52 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
23 / 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
  • Minor
    Its description is nearly the same as synchroteam_get_invoice's (similarity 0.78); only the names and schemas tell them apart. Say in this description when to use synchroteam_get_invoice instead.confusable_pair
  • Minor
    Says nothing about what it returns.no_return_info

synchroteam_start_job

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

synchroteam_schedule_job

53 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
18 / 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
  • Minor
    Arguments without a description: technician.id, technician.login.param_no_description
  • Minor
    Says nothing about what it returns.no_return_info

synchroteam_get_job_photos

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
    Says nothing about what it returns.no_return_info

synchroteam_create_job

57 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
20 / 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: contact_first_name, contact_last_name, contact_email, contact_phone, contact_mobile.param_no_description
  • Minor
    Says nothing about what it returns.no_return_info

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