redm-mcp

List RedM doc namespaces

list_namespaces

Read-only

Orient yourself: list available doc categories and their namespaces. Use once at session start (or when unsure) before applying a category= / namespace= filter to browse / semantic_search. NOT a content search. Categories: natives (PLAYER, ENTITY, VEHICLE, …), vorp, rsgcore, oxmysql, discoveries (AI, weapons, peds, animations, clothes, objects, …), jo_libs (menu, notification, callback, framework-bridge, …, dev_resources, redm_scripts), cfx (Cfx runtime/scripting API from docs.fivem.net: scripting-reference, scripting-manual, server-manual, client-manual, resources, cookbook, …), guides, learnings.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`category`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`categories`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 14, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "natives",
-  "vorp",
-  "rsgcore",
-  "oxmysql",
-  "discoveries",
-  "jo_libs",
-  "guides",
-  "learnings"
-]New value: +[
+  "natives",
+  "vorp",
+  "rsgcore",
+  "oxmysql",
+  "discoveries",
+  "jo_libs",
+  "cfx",
+  "guides",
+  "learnings"
+]

Changed3 schema fields changedAug 9, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "categories": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "namespaces": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "category",
+          "namespaces"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "categories"
+  ],
+  "type": "object"
+}

First observedMay 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: it is an orientation/listing call, explicitly not a content search, and scoped to a fixed set of doc sources. It does not discuss cost, caching, or output shape, but the output schema covers returns.

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 orientation purpose and the when-to-use rule before the category enumeration, and the 'NOT a content search' exclusion is placed early. The long parenthetical namespace lists are useful but slightly noisy; they could be trimmed without losing function.

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?

For a one-param, read-only listing tool with an output schema, the description supplies everything needed: purpose, timing, exclusions, and the populated category values. Nothing critical is missing, though noting that the filter is optional would make it fully self-contained.

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 description coverage is 0% and the single optional `category` param has an enum, so the description must carry the load — and it does, enumerating each category with representative sub-namespaces (PLAYER, ENTITY, VEHICLE for natives; menu, notification, callback for jo_libs). It adds real meaning beyond the bare enum list, though it never states explicitly that omitting `category` returns everything.

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?

Specific verb+resource (list doc categories/namespaces) with an explicit negative scope statement ('NOT a content search') that separates it from the sibling search tools. An agent can tell exactly what this returns without opening the schema or siblings.

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?

States precisely when to call it ('once at session start, or when unsure') and what it enables ('before applying a `category=` / `namespace=` filter to browse / semantic_search'). Explicit alternatives are named, so the routing decision is unambiguous.

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

All redm-mcp 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.