Nausika: tool descriptions scored app.nausika/mcp

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

Scores, issues and names only

This page shows how Nausika (app.nausika/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.nausika/mcp

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

Across the server

No server-wide issues.

Tools

nausika_get_boat_profile

62 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 22 / 25
Return value: 8 / 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
No `required` list, so every argument is optional.no_required

nausika_get_favorites

65 / 100Cloudy

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

nausika_get_ratings

67 / 100Cloudy

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

nausika_get_routes

67 / 100Cloudy

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

nausika_manage_boat_profile

67 / 100Cloudy

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

nausika_manage_route

69 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 24 / 25
Return value: 8 / 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
String arguments with no constraint or example: legs[].departure_date, legs[].notes.loose_string_param

nausika_manage_favorite

70 / 100Clear

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

nausika_manage_rating

70 / 100Clear

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

nausika_describe_place_schema

74 / 100Clear

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

nausika_seasonal_forecast

75 / 100Clear

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

nausika_calculator

77 / 100Clear

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

Major
Says nothing about when to use it, or when not to.no_usage_context

nausika_convert_coordinates

77 / 100Clear

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

nausika_geocode

77 / 100Clear

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

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

nausika_is_water

77 / 100Clear

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

nausika_sea_route

79 / 100Clear

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

No issues.

nausika_search_places

79 / 100Clear

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

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

nausika_get_place

82 / 100Clear

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

No issues.

nausika_tides

82 / 100Clear

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

No issues.

nausika_marine_forecast

92 / 100Clear

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