Forecall
Failure recordsDocs
All scored servers

Weather MCP Server: tool descriptions scored

tools/list taken
(UTC)
From
smithery.ai/servers/isdaniel/mcp_weather_server
Homepage
github.com
Scoring rules
v2

Scores, issues and names only

This page shows how Weather MCP Server'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.

This copy comes from Smithery's registry, which keeps each tool's name, description and input schema, but no output schema, annotations or instructions. Points for return values and for marking destructive tools can come out lower than the server's own tools/list would give.

A server with a public URL can be scored as it is today: score from a URL

servers/isdaniel-mcp-weather-server
Average score
33.1 / 100Rain
Tools
8
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
get_weather_detailsget_air_quality_details0.820.40

Tools

convert_time

26 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
15 / 25
Return value
0 / 15
Constraints and side effects
0 / 10
Examples
5 / 10
  • Major
    The description only restates the name (7 words).restates_name
  • Major
    The description is too short (7 words).too_short
  • 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
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

get_current_datetime

26 / 100Rain

Purpose
6 / 20
When to use
0 / 20
Arguments
15 / 25
Return value
0 / 15
Constraints and side effects
0 / 10
Examples
5 / 10
  • Major
    The description only restates the name (6 words).restates_name
  • Major
    The description is too short (6 words).too_short
  • 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
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

get_weather_byDateTimeRange

32 / 100Rain

Purpose
17 / 20
When to use
0 / 20
Arguments
15 / 25
Return value
0 / 15
Constraints and side effects
0 / 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
    Says nothing about what it returns.no_return_info
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

get_weather_details

32 / 100Rain

Purpose
17 / 20
When to use
0 / 20
Arguments
15 / 25
Return value
0 / 15
Constraints and side effects
0 / 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 get_air_quality_details's (similarity 0.82); only the names and schemas tell them apart. Say in this description when to use get_air_quality_details instead.confusable_pair
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

get_air_quality

35 / 100Rain

Purpose
20 / 20
When to use
0 / 20
Arguments
15 / 25
Return value
0 / 15
Constraints and side effects
0 / 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
    Says nothing about what it returns.no_return_info
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

get_air_quality_details

35 / 100Rain

Purpose
20 / 20
When to use
0 / 20
Arguments
15 / 25
Return value
0 / 15
Constraints and side effects
0 / 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 get_weather_details's (similarity 0.82); only the names and schemas tell them apart. Say in this description when to use get_weather_details instead.confusable_pair
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

get_timezone_info

37 / 100Rain

Purpose
17 / 20
When to use
0 / 20
Arguments
15 / 25
Return value
0 / 15
Constraints and side effects
0 / 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
  • Minor
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

get_current_weather

42 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
15 / 25
Return value
7 / 15
Constraints and side effects
0 / 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
    No constraints, side effects, auth or rate limits described, and no annotations.no_constraints

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