raumnebenan

List articles

list_articles

Read-onlyIdempotent

Lists published articles as a compact index (slug, uuid, title, category, story slug). Use it to browse available articles. Filter with optional category (foundation, sense, discover, focus, deliver). Set include_summary: true to include the summary excerpt for each article. For finding articles on a specific topic or method, prefer search_articles. To read full article body markdown, call get_article_details_by_slugs with the returned article_slug values. Optional page/per return a slice and next_page while more remain; without them the complete list is returned.

Input Schema

Name	Required	Description
`per`	No	Optional items per page (default 20 when page is set, max 100).
`page`	No	Optional 1-based page. Omit both page and per to receive the complete list.
`category`	No	Optional category filter to restrict articles to one topic (foundation, sense, discover, focus, deliver).
`include_summary`	No	When true, includes the 1-2 sentence summary for each article. Defaults to false for a lean compact index.

Output Schema

Name	Required	Description	Default
`data`	Yes
`source`	Yes
`retrieved_at`	Yes
`copyright_holder`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 17, 2026

addedInput schema / properties / page

Added value: +{
+  "description": "Optional 1-based page. Omit both page and per to receive the complete list.",
+  "maximum": 10000,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / per

Added value: +{
+  "description": "Optional items per page (default 20 when page is set, max 100).",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / properties / data / properties / next_page

Added value: +{
+  "description": "The next page number; absent on the last page.",
+  "minimum": 2,
+  "type": "integer"
+}

addedOutput schema / properties / data / properties / page

Added value: +{
+  "description": "The returned page (1-based).",
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / properties / data / properties / per

Added value: +{
+  "description": "Items per page.",
+  "minimum": 1,
+  "type": "integer"
+}

Changed1 schema field changedOct 16, 2026
- addedInput schema / properties / category / minLength
```
Added value: +1
```

Changed7 schema fields changedOct 16, 2026

addedInput schema / properties / category

Added value: +{
+  "description": "Optional category filter to restrict articles to one topic (foundation, sense, discover, focus, deliver).",
+  "enum": [
+    "foundation",
+    "sense",
+    "discover",
+    "focus",
+    "deliver"
+  ],
+  "maxLength": 50,
+  "type": "string"
+}

addedInput schema / properties / include_summary

Added value: +{
+  "description": "When true, includes the 1-2 sentence summary for each article. Defaults to false for a lean compact index.",
+  "type": "boolean"
+}

addedOutput schema / properties / data

Added value: +{
+  "properties": {
+    "articles": {
+      "description": "The list of article overviews.",
+      "items": {
+        "properties": {
+          "article_slug": {
+            "type": "string"
+          },
+          "article_uuid": {
+            "format": "uuid",
+            "type": "string"
+          },
+          "category": {
+            "type": "string"
+          },
+          "story_slug": {
+            "type": "string"
+          },
+          "summary": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "article_slug",
+          "article_uuid",
+          "title"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "The total number of articles.",
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total",
+    "articles"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / retrieved_at

Added value: +{
+  "format": "date-time",
+  "type": "string"
+}

removedOutput schema / properties / source_friendly_url
```
Removed value: -{
-  "type": "string"
-}
```

removedOutput schema / properties / stories

Removed value: -{
-  "items": {
-    "properties": [],
-    "required": [],
-    "type": "object"
-  },
-  "type": "array"
-}

changedOutput schema / required

Previous value: -[]New value: +[
+  "source",
+  "copyright_holder",
+  "retrieved_at",
+  "data"
+]

First observedJun 2, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond that: the exact return shape, the include_summary toggle, and pagination via next_page when page/per are supplied.

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?

Front-loaded with the core purpose and return shape, then routing guidance. It is somewhat long but each sentence carries actionable information with no filler.

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

Completeness5/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 need no further explanation. The description covers purpose, filters, pagination, and sibling routing, leaving no gap an agent needs to call it correctly.

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 the baseline is 3. The description goes further by explaining the include_summary effect ('summary excerpt'), the page/per slice semantics, and the next_page return signal, adding value beyond the schema.

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?

States a specific verb and resource ('Lists published articles as a compact index') and enumerates the returned fields (slug, uuid, title, category, story slug). It clearly distinguishes itself from search_articles and get_article_details_by_slugs.

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

Usage Guidelines5/5

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

Explicitly names when to use it ('browse available articles') and when not to ('For finding articles on a specific topic or method, prefer search_articles'), plus a hand-off instruction to get_article_details_by_slugs for full bodies. Alternatives and conditions are fully spelled out.

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

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

Resources

Need Help?