appdesigns App Store screenshots: tool descriptions scored click.appdesigns/screenshots

tools/list taken: 2026-11-02 (UTC)
From: Official MCP Registry
Connected to: https://appdesigns.click/api/mcp
Homepage: appdesigns.click/mcp
Repository: github.com/haider-nawaz/app-store-screenshots-mcp
Scoring rules: v2
Removal: support@forecall.dev

Scores, issues and names only

This page shows how appdesigns App Store screenshots (click.appdesigns/screenshots)'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/click.appdesigns/screenshots

Average score: 71.0 / 100Clear
Tools: 19
Near-identical descriptions: 0

Across the server

No server-wide issues.

Tools

finish_project

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

update_project

59 / 100Cloudy

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

60 / 100Cloudy

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

update_design

60 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 19 / 25
Return value: 7 / 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: changes[].background, changes[].background.gradient.type, changes[].loop, changes[].loop.effects, changes[].loop.effects[].speed, changes[].title.param_no_description

export_asset

65 / 100Cloudy

Purpose: 20 / 20
When to use: 10 / 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

list_projects

65 / 100Cloudy

Purpose: 20 / 20
When to use: 10 / 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_asset

67 / 100Cloudy

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

Minor
No `required` list, so every argument is optional.no_required

get_design_guide

67 / 100Cloudy

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

Minor
No `required` list, so every argument is optional.no_required

edit_asset

70 / 100Clear

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

Minor
Arguments without a description: changes[].to, changes[].background, changes[].background.gradient.type, changes[].title.param_no_description
Minor
Says nothing about what it returns.no_return_info

feature_app

73 / 100Clear

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

Minor
Says nothing about what it returns.no_return_info

create_design

75 / 100Clear

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

Minor
Arguments without a description: variants[].background, variants[].background.gradient.type, variants[].layers[].motion, variants[].loop, variants[].loop.effects, variants[].loop.effects[].speed.param_no_description

get_export

75 / 100Clear

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

No issues.

make_screenshot_set

75 / 100Clear

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

replace_screenshots

77 / 100Clear

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

Minor
No `required` list, so every argument is optional.no_required

get_workflow

80 / 100Clear

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

No issues.

save_to_account

80 / 100Clear

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

No issues.

search_library

80 / 100Clear

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

Minor
The description mentions none of its 3 or more arguments.params_not_in_description

translate_asset

80 / 100Clear

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

No issues.

create_project

87 / 100Clear

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