All scored servers

Upforge: tool descriptions scored io.github.upforge-dev/upforge

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

Scores, issues and names only

This page shows how Upforge (io.github.upforge-dev/upforge)'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.github.upforge-dev/upforge
Average score
56.8 / 100Cloudy
Tools
20
Near-identical descriptions
0

Across the server

No server-wide issues.

Tools

list_articles

38 / 100Rain

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

submit_project_review

46 / 100Cloudy

Purpose
17 / 20
When to use
5 / 20
Arguments
14 / 25
Return value
0 / 15
Constraints and side effects
10 / 10
Examples
0 / 10
  • Minor
    Arguments without a description: human_approved, rights_to_submit, review_only.param_no_description
  • Minor
    The meaning of the boolean argument human_approved is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument rights_to_submit is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument review_only is unclear.vague_boolean
  • Minor
    Says nothing about what it returns.no_return_info

get_article

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

get_review_status

52 / 100Cloudy

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

prepare_review_upload

52 / 100Cloudy

Purpose
17 / 20
When to use
10 / 20
Arguments
8 / 25
Return value
7 / 15
Constraints and side effects
10 / 10
Examples
0 / 10
  • Major
    Arguments without a description: rights_to_submit, retention_accepted.param_no_description
  • Minor
    The meaning of the boolean argument rights_to_submit is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument retention_accepted is unclear.vague_boolean

find_consultation_times

53 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
11 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
10 / 10
  • Minor
    Arguments without a description: address.street, address.city, address.postalCode, address.country.param_no_description
  • Minor
    String arguments with no constraint or example: address.street, address.city, address.region, address.postalCode, address.country.loose_string_param
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

check_service_area

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

finalize_review_upload

54 / 100Cloudy

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

No issues.

get_services

54 / 100Cloudy

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

request_site_audit

55 / 100Cloudy

Purpose
20 / 20
When to use
10 / 20
Arguments
18 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    String arguments with no constraint or example: company, phone.loose_string_param
  • Minor
    Says nothing about what it returns.no_return_info

book_consultation

56 / 100Cloudy

Purpose
20 / 20
When to use
10 / 20
Arguments
14 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    Arguments without a description: address.street, address.city, address.postalCode, address.country.param_no_description
  • Minor
    String arguments with no constraint or example: company, address.street, address.city, address.region, address.postalCode, address.country.loose_string_param
  • 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

get_company_overview

57 / 100Cloudy

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

get_pricing

57 / 100Cloudy

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

get_industries

59 / 100Cloudy

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

get_review_requirements

59 / 100Cloudy

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

search_faq

60 / 100Cloudy

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

get_case_studies

64 / 100Cloudy

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

ask_echo

71 / 100Clear

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

request_consultation

71 / 100Clear

Purpose
20 / 20
When to use
20 / 20
Arguments
19 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    String arguments with no constraint or example: company.loose_string_param
  • Minor
    Says nothing about what it returns.no_return_info

match_capability

75 / 100Clear

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