Lobsters

Get Hottest

get_hottest

Read-onlyIdempotent

Get trending stories from Lobsters. Returns title, URL, score, comment count, and tags for each story.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`count`	No	Number of stories returned
`stories`	No	List of trending stories

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedJun 2, 2026

changedOutput schema / properties / stories / items / properties / description / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
```

removedOutput schema / properties / stories / items / properties / downvotes

Removed value: -{
-  "description": "Number of downvotes",
-  "type": "number"
-}

removedOutput schema / properties / stories / items / properties / submitter

Removed value: -{
-  "description": "Username of story submitter",
-  "type": "string"
-}

removedOutput schema / properties / stories / items / properties / upvotes

Removed value: -{
-  "description": "Number of upvotes",
-  "type": "number"
-}

removedOutput schema / properties / stories / items / required

Removed value: -[
-  "short_id",
-  "url",
-  "comments_url",
-  "title",
-  "score",
-  "upvotes",
-  "downvotes",
-  "comment_count",
-  "created_at",
-  "submitter",
-  "tags",
-  "description"
-]

removedOutput schema / required

Removed value: -[
-  "count",
-  "stories"
-]

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of stories returned",
+      "type": "number"
+    },
+    "stories": {
+      "description": "List of trending stories",
+      "items": {
+        "properties": {
+          "comment_count": {
+            "description": "Number of comments",
+            "type": "number"
+          },
+          "comments_url": {
+            "description": "URL to view comments on Lobsters",
+            "type": "string"
+          },
+          "created_at": {
+            "description": "ISO timestamp of story creation",
+            "type": "string"
+          },
+          "description": {
+            "description": "Plain text description or null",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "downvotes": {
+            "description": "Number of downvotes",
+            "type": "number"
+          },
+          "score": {
+            "description": "Total score (upvotes - downvotes)",
+            "type": "number"
+          },
+          "short_id": {
+            "description": "Unique short ID for the story",
+            "type": "string"
+          },
+          "submitter": {
+            "description": "Username of story submitter",
+            "type": "string"
+          },
+          "tags": {
+            "description": "Tags associated with the story",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "title": {
+            "description": "Story title",
+            "type": "string"
+          },
+          "upvotes": {
+            "description": "Number of upvotes",
+            "type": "number"
+          },
+          "url": {
+            "description": "Story URL",
+            "type": "string"
+          }
+        },
+        "required": [
+          "short_id",
+          "url",
+          "comments_url",
+          "title",
+          "score",
+          "upvotes",
+          "downvotes",
+          "comment_count",
+          "created_at",
+          "submitter",
+          "tags",
+          "description"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "stories"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026
- addedInput schema / examples
```
Added value: +[
+  {}
+]
```
First observedApr 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering safety and side effects. The description adds value by specifying the return fields and data source, but does not mention any additional behavioral traits (e.g., rate limits, authentication).

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

Conciseness5/5

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

Two sentences, no extraneous information. The primary action and return fields are front-loaded, making it easy for an agent to parse quickly.

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?

Given the tool has no parameters, a simple return, and an output schema (per context signals), the description adequately covers what the agent needs to know: source and return fields. Could mention ordering or limits, but not necessary given the tool's simplicity.

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?

The input schema has no parameters, and schema description coverage is 100%. The description does not need to explain parameters. Baseline of 4 is appropriate for zero-parameter tools.

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 uses a specific verb ('Get') and resource ('trending stories from Lobsters'), and lists the returned fields (title, URL, score, comment count, tags). It clearly distinguishes from siblings like get_newest (newest vs trending) and get_story (single story vs list).

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

Usage Guidelines3/5

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

The description implies use for trending content but does not explicitly state when to use this tool versus alternatives like get_newest or get_story. No exclusion criteria or context is provided.

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

All Lobsters 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.