Nausika

by app.nausika

Overview Discussions Admin

Get Ratings

nausika_get_ratings

Read-onlyIdempotent

View ratings for a place (aggregate + your own) or list all your ratings.

Inputs: place_id, my_only, limit, offset.

Examples:

Place ratings: place_id="a1b2c3d4" (8-char short-id or full UUID)
My ratings: my_only=true

Tip: ratings are visible in nausika_search_places results to help other sailors.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nausika_get_ratings"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max results
`offset`	No	Offset for pagination
`my_only`	No	List only your own ratings
`place_id`	No	Get ratings for a specific place — full UUID or 8+ char hex prefix from nausika_search_places

Output Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`ratings`	No
`aggregate`	No
`my_rating`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedMay 20, 2026

changedInput schema / properties / place_id / description

Previous value: -"Get ratings for a specific place"New value: +"Get ratings for a specific place — full UUID or 8+ char hex prefix from nausika_search_places"

changedInput schema / properties / place_id / examples

Previous value: -[
-  "a1b2c3d4-e5f6-7890-abcd-ef0123456789"
-]New value: +[
+  "a1b2c3d4-e5f6-7890-abcd-ef0123456789",
+  "a1b2c3d4"
+]

removedInput schema / properties / place_id / format
```
Removed value: -"uuid"
```
addedInput schema / properties / place_id / maxLength
```
Added value: +64
```
addedInput schema / properties / place_id / minLength
```
Added value: +8
```

removedInput schema / properties / place_id / pattern

Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000)$"

Changed30 schema fields changedMay 18, 2026

addedInput schema / properties / limit / examples
```
Added value: +[
+  50
+]
```
addedInput schema / properties / my_only / examples
```
Added value: +[
+  true
+]
```
addedInput schema / properties / offset / examples
```
Added value: +[
+  0
+]
```
addedInput schema / properties / offset / maximum
```
Added value: +9007199254740991
```

addedInput schema / properties / place_id / examples

Added value: +[
+  "a1b2c3d4-e5f6-7890-abcd-ef0123456789"
+]

addedInput schema / properties / place_id / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000)$"

changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```
changedOutput schema / properties / aggregate / additionalProperties
```
Previous value: -trueNew value: +{}
```

addedOutput schema / properties / aggregate / properties / avg_rating / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / aggregate / properties / avg_rating / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
addedOutput schema / properties / limit / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / limit / minimum
```
Added value: +-9007199254740991
```

changedOutput schema / properties / my_rating / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {
-      "comment": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "created_at": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "format": "date-time",
-            "type": "string"
-          }
-        ]
-      },
-      "id": {
-        "type": "string"
-      },
-      "place_id": {
-        "type": "string"
-      },
-      "score": {
-        "type": "number"
-      },
-      "updated_at": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "format": "date-time",
-            "type": "string"
-          }
-        ]
-      },
-      "user_id": {
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "comment": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "created_at": {
+        "type": "string"
+      },
+      "id": {
+        "type": "string"
+      },
+      "place_id": {
+        "type": "string"
+      },
+      "score": {
+        "type": "number"
+      },
+      "updated_at": {
+        "type": "string"
+      },
+      "user_id": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / offset / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / offset / minimum
```
Added value: +-9007199254740991
```
changedOutput schema / properties / ratings / items / additionalProperties
```
Previous value: -trueNew value: +{}
```
removedOutput schema / properties / ratings / items / properties / comment / $ref
```
Removed value: -"#/properties/my_rating/anyOf/0/properties/comment"
```

addedOutput schema / properties / ratings / items / properties / comment / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / ratings / items / properties / created_at / $ref
```
Removed value: -"#/properties/my_rating/anyOf/0/properties/created_at"
```
addedOutput schema / properties / ratings / items / properties / created_at / type
```
Added value: +"string"
```
removedOutput schema / properties / ratings / items / properties / id / $ref
```
Removed value: -"#/properties/my_rating/anyOf/0/properties/id"
```
addedOutput schema / properties / ratings / items / properties / id / type
```
Added value: +"string"
```
removedOutput schema / properties / ratings / items / properties / place_id / $ref
```
Removed value: -"#/properties/my_rating/anyOf/0/properties/place_id"
```
addedOutput schema / properties / ratings / items / properties / place_id / type
```
Added value: +"string"
```
removedOutput schema / properties / ratings / items / properties / score / $ref
```
Removed value: -"#/properties/my_rating/anyOf/0/properties/score"
```
addedOutput schema / properties / ratings / items / properties / score / type
```
Added value: +"number"
```
removedOutput schema / properties / ratings / items / properties / updated_at / $ref
```
Removed value: -"#/properties/my_rating/anyOf/0/properties/updated_at"
```
addedOutput schema / properties / ratings / items / properties / updated_at / type
```
Added value: +"string"
```
removedOutput schema / properties / ratings / items / properties / user_id / $ref
```
Removed value: -"#/properties/my_rating/anyOf/0/properties/user_id"
```
addedOutput schema / properties / ratings / items / properties / user_id / type
```
Added value: +"string"
```

First observedMay 18, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds behavioral detail beyond annotations: it explains the two distinct output modes (aggregate+own vs. own-only) and notes that ratings appear in search results. This is useful context that complements the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-organized with a brief overview, input list, examples, and a helpful tip. It's not overly verbose, though the tip about search results is slightly tangential. Overall, every section earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values are covered. The description handles the two primary usage contexts (place ratings and my ratings) and parameter combinations implied by examples. Minor gaps like behavior when both place_id and my_only are set are not addressed, but the complexity is moderate and adequately covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a baseline of 3 applies. The description adds extra meaning by clarifying place_id accepts either a full UUID or an 8-char short-id, and gives concrete examples for limit/offset usage. This adds value beyond the schema's property descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'View ratings for a place (aggregate + your own) or list all your ratings.' It clearly distinguishes the two main modes and differentiates from sibling tools like nausika_manage_rating, which presumably handles write operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context through examples: use place_id for place ratings, my_only=true for your own. It implies when to use this read-only tool versus write tools like nausika_manage_rating. No explicit exclusions, but the examples give actionable usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nausika tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.