Flaim Fantasy: tool descriptions scored app.flaim/mcp

tools/list taken: 2026-11-02 (UTC)
From: Official MCP Registry
Connected to: https://api.flaim.app/mcp
Homepage: flaim.app
Repository: github.com/jdguggs10/flaim-fantasy
Scoring rules: v2
Removal: support@forecall.dev

Scores, issues and names only

This page shows how Flaim Fantasy (app.flaim/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.flaim/mcp

Average score: 84.8 / 100Clear
Tools: 17
Near-identical descriptions: 2

Across the server

Minor
The server's instructions are 8884 characters. Claude Code reads only the first 2,048 by default (Codex 0.154.0 reads them whole). Put what the server is for first.instructions_long

Tools whose descriptions are nearly the same

2 of 2 pairs shown, highest description similarity first.
Tool	Tool	Description similarity	Name similarity
open_flaim_home	open_flaim_home_tab	0.72	0.75
delete_flaim_home_ask	reorder_flaim_home_asks	0.61	0.33

Tools

delete_flaim_home_ask

67 / 100Cloudy

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

Minor
Its description is nearly the same as reorder_flaim_home_asks's (similarity 0.61); only the names and schemas tell them apart. Say in this description when to use reorder_flaim_home_asks 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

reorder_flaim_home_asks

67 / 100Cloudy

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

Minor
Its description is nearly the same as delete_flaim_home_ask's (similarity 0.61); only the names and schemas tell them apart. Say in this description when to use delete_flaim_home_ask instead.confusable_pair
Minor
Required identifiers whose description does not say where the value comes from: ids. Name the tool or the place that returns it, or models look it up first.id_source_missing

refresh_leagues

72 / 100Clear

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

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

save_flaim_home_ask

72 / 100Clear

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

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

get_flaim_home_league

73 / 100Clear

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

No issues.

open_flaim_home

77 / 100Clear

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

Minor
Its description is nearly the same as open_flaim_home_tab's (similarity 0.72); only the names and schemas tell them apart. Say in this description when to use open_flaim_home_tab instead.confusable_pair

get_ancient_history

82 / 100Clear

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

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

open_flaim_home_tab

84 / 100Clear

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

Minor
Its description is nearly the same as open_flaim_home's (similarity 0.72); only the names and schemas tell them apart. Say in this description when to use open_flaim_home instead.confusable_pair
Minor
No `required` list, so every argument is optional.no_required

get_league_info

85 / 100Clear

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

No issues.

get_user_session

90 / 100Clear

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

No issues.

get_transactions

92 / 100Clear

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

No issues.

get_draft

94 / 100Clear

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

No issues.

get_free_agents

97 / 100Clear

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

Minor
The description is long (652 words). It helps selection but costs steps and tokens.too_long

get_matchups

97 / 100Clear

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

Minor
The description is long (512 words). It helps selection but costs steps and tokens.too_long

get_roster

97 / 100Clear

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

Minor
The description is long (462 words). It helps selection but costs steps and tokens.too_long

get_players

98 / 100Clear

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

No issues.

get_standings

98 / 100Clear

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

Minor
The description is long (527 words). It helps selection but costs steps and tokens.too_long

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