All scored servers

Recao: tool descriptions scored app.recao/recao-mcp

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

Scores, issues and names only

This page shows how Recao (app.recao/recao-mcp)'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/app.recao/recao-mcp
Average score
54.4 / 100Cloudy
Tools
17
Near-identical descriptions
1

Across the server

Tools whose descriptions are nearly the same

1 of 1 pairs shown, highest description similarity first.
ToolToolDescription similarityName similarity
clips_statusassemble_status0.600.33

Tools

get_ad_details

34 / 100Rain

Purpose
20 / 20
When to use
0 / 20
Arguments
7 / 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: adId, datePreset.param_no_description
  • Minor
    String arguments with no constraint or example: adId.loose_string_param
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: adId. Name the tool or the place that returns it, or models look it up first.id_source_missing

get_playbook

34 / 100Rain

Purpose
20 / 20
When to use
0 / 20
Arguments
2 / 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: slug.param_no_description
  • Minor
    String arguments with no constraint or example: slug.loose_string_param
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info

upgrade

37 / 100Rain

Purpose
20 / 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
  • Major
    Arguments without a description: plan.param_no_description
  • Minor
    Says nothing about what it returns.no_return_info

memory_recall

44 / 100Cloudy

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

get_competitor_ads

45 / 100Cloudy

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

memory_index

52 / 100Cloudy

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

search_app_advertiser

52 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
18 / 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: types.param_no_description

whoami

52 / 100Cloudy

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

roadmap_status

54 / 100Cloudy

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

memory_note

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

generate_avatar

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

usage

60 / 100Cloudy

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

generate_clips

61 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
22 / 25
Return value
7 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    String arguments with no constraint or example: scenes[].camera, scenes[].energy.loose_string_param

assemble_status

62 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
20 / 25
Return value
7 / 15
Constraints and side effects
10 / 10
Examples
0 / 10
  • Minor
    Its description is nearly the same as clips_status's (similarity 0.60); only the names and schemas tell them apart. Say in this description when to use clips_status instead.confusable_pair

clips_status

62 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
20 / 25
Return value
7 / 15
Constraints and side effects
10 / 10
Examples
0 / 10
  • Minor
    Its description is nearly the same as assemble_status's (similarity 0.60); only the names and schemas tell them apart. Say in this description when to use assemble_status instead.confusable_pair

assemble_video

78 / 100Clear

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

No issues.

sign_up

84 / 100Clear

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