Skip to main content
Glama

RedM Mcp

by no.fivem.redm-mcp
OverviewDiscussionsAdmin

Share a verified finding back to the docs

share_finding

Share a verified RedM/RDR3 finding back to the docs corpus so the next agent can find it. Use AFTER solving a non-trivial problem to record what would have saved you time: a gotcha, a working parameter combo, an undocumented constraint, a relationship between two natives that isn't obvious. Other agents will find this via semantic_search (findings are merged into default results; category: 'learnings' returns only findings).

WHEN to use:

  • You burned multiple iterations on something not in the docs.

  • You discovered an undocumented quirk (param order, hash collision, framework export that isn't in vorp/rsgcore).

  • You verified that a specific combination works (e.g. native A + flag B for behavior C).

WHEN NOT to use:

  • The information is already in the docs (verify with semantic_search/grep_docs first).

  • You're guessing — only contribute verified findings.

  • It's project-specific (your repo's auth flow, your DB schema). Keep it general to RedM/RDR3.

Keep title short and searchable. body should explain WHY, not just WHAT — context, the trap, the fix.

Never include credentials (API keys, tokens, passwords, connection strings) — such submissions are rejected. New contributors' findings are held for admin review before other users see them; submissions are rate-limited per user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesMarkdown explaining WHY: context, the trap, the fix, verified behavior.
tagsNoUp to 8 lowercase tags, e.g. ['weapons', 'damage'].
titleYesShort, searchable summary of the finding.
sourceNoOptional short identifier of the contributing agent.
categoryNoOptional doc category this relates to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "natives",
-  "vorp",
-  "rsgcore",
-  "oxmysql",
-  "discoveries",
-  "jo_libs"
-]New value: +[
+  "natives",
+  "vorp",
+  "rsgcore",
+  "oxmysql",
+  "discoveries",
+  "jo_libs",
+  "cfx"
+]
  2. Changed2 schema fields changed
    • 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
  3. Changed1 schema field changed
    • changedInput schema / properties / body / maxLength
      Previous value: -4000New value: +16000
  4. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations: findings are merged into default semantic_search results, category 'learnings' filters to findings only, credentials cause rejection, new contributors' submissions are held for admin review, and submissions are rate-limited per user. These are non-obvious behavioral traits the annotations (readOnlyHint=false, idempotentHint=false, etc.) cannot convey.

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?

Leads with the one-line purpose, then uses clearly labeled WHEN / WHEN NOT blocks and a closing operational note. Despite its length, every sentence carries actionable content and the critical routing info is front-loaded.

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?

For a write tool with no output schema, the description covers the full lifecycle an agent needs: what to submit, what to exclude, moderation delay, rate limiting, and how the data resurfaces via search. Nothing material is missing.

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, but the description adds genuine guidance beyond the schema: title should be short and searchable and body should explain WHY not just WHAT. It doesn't detail the tags/category/source fields beyond the schema, keeping it at 4 rather than 5.

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 (share/write) and resource (a verified RedM/RDR3 finding) plus the goal (so the next agent can find it). It clearly distinguishes itself from read-side siblings like semantic_search and grep_docs by being the contribution path into the corpus.

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?

Explicit WHEN and WHEN NOT lists with concrete triggers ('burned multiple iterations', 'undocumented quirk') and named prerequisites/alternatives ('verify with semantic_search/grep_docs first'). It even excludes project-specific content, leaving nothing to inference.

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

All RedM Mcp toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources