Forecall
Failure recordsDocs
All scored servers

Zendesk MCP by usefulapi: tool descriptions scored io.usefulapi/zendesk

tools/list taken
(UTC)
From
Official MCP Registry
Connected to
https://zendesk.usefulapi.io/mcp
Homepage
usefulapi.io/zendesk/
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 Zendesk MCP by usefulapi (io.usefulapi/zendesk)'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/zendesk
Average score
48.2 / 100Cloudy
Tools
19
Near-identical descriptions
5

Across the server

Tools whose descriptions are nearly the same

5 of 5 pairs shown, highest description similarity first.
ToolToolDescription similarityName similarity
zendesk_list_ticketszendesk_list_organizations0.700.50
zendesk_get_ticketzendesk_get_user0.600.50
zendesk_get_ticketzendesk_get_organization0.600.50
zendesk_get_userzendesk_get_organization0.600.50
zendesk_get_ticketzendesk_get_ticket_metrics0.540.75

Tools

zendesk_list_groups

33 / 100Rain

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

zendesk_list_organizations

36 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
0 / 15
Constraints and side effects
10 / 10
Examples
0 / 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
    Its description is nearly the same as zendesk_list_tickets's (similarity 0.70); only the names and schemas tell them apart. Say in this description when to use zendesk_list_tickets instead.confusable_pair
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

zendesk_list_tickets

43 / 100Cloudy

Purpose
13 / 20
When to use
0 / 20
Arguments
20 / 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
  • Minor
    Its description is nearly the same as zendesk_list_organizations's (similarity 0.70); only the names and schemas tell them apart. Say in this description when to use zendesk_list_organizations instead.confusable_pair
  • 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

zendesk_list_macros

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

zendesk_get_organization

47 / 100Cloudy

Purpose
17 / 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
    Its description is nearly the same as zendesk_get_ticket's (similarity 0.60); only the names and schemas tell them apart. Say in this description when to use zendesk_get_ticket instead.confusable_pair
  • Minor
    Its description is nearly the same as zendesk_get_user's (similarity 0.60); only the names and schemas tell them apart. Say in this description when to use zendesk_get_user 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: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

zendesk_get_ticket

47 / 100Cloudy

Purpose
17 / 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
    Its description is nearly the same as zendesk_get_user's (similarity 0.60); only the names and schemas tell them apart. Say in this description when to use zendesk_get_user instead.confusable_pair
  • Minor
    Its description is nearly the same as zendesk_get_organization's (similarity 0.60); only the names and schemas tell them apart. Say in this description when to use zendesk_get_organization instead.confusable_pair
  • Minor
    Its description is nearly the same as zendesk_get_ticket_metrics's (similarity 0.54); only the names and schemas tell them apart. Say in this description when to use zendesk_get_ticket_metrics 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: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

zendesk_get_user

47 / 100Cloudy

Purpose
17 / 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
    Its description is nearly the same as zendesk_get_ticket's (similarity 0.60); only the names and schemas tell them apart. Say in this description when to use zendesk_get_ticket instead.confusable_pair
  • Minor
    Its description is nearly the same as zendesk_get_organization's (similarity 0.60); only the names and schemas tell them apart. Say in this description when to use zendesk_get_organization 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: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

zendesk_list_ticket_comments

47 / 100Cloudy

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

zendesk_create_ticket

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

zendesk_list_satisfaction_ratings

49 / 100Cloudy

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

zendesk_list_ticket_fields

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

zendesk_list_views

49 / 100Cloudy

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

zendesk_execute_view

51 / 100Cloudy

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

zendesk_update_ticket

51 / 100Cloudy

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

zendesk_add_ticket_comment

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: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

zendesk_search_users

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

zendesk_get_ticket_metrics

54 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 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
    Its description is nearly the same as zendesk_get_ticket's (similarity 0.54); only the names and schemas tell them apart. Say in this description when to use zendesk_get_ticket instead.confusable_pair
  • 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

zendesk_search

57 / 100Cloudy

Purpose
17 / 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
    The description mentions none of its 3 or more arguments.params_not_in_description
  • Minor
    Says nothing about what it returns.no_return_info

zendesk_current_user

59 / 100Cloudy

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

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