fivem-mcp-server

Overview Schema Source Related Servers Discussions Admin

Mouse wheel

scroll

Simulate mouse wheel movement to navigate NUI lists and game menus in FiveM, using amount positive for up and negative for down.

Instructions

Scroll the wheel (positive = up). NUI lists respond to it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "amount": "<amount>"
    },
    "name": "scroll"
  }
}

Input Schema

Name	Required	Description	Default
`amount`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Oct 17, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower. The description usefully adds the direction convention and that NUI lists are the responsive target, but says nothing about focus requirements, rate limits, or repeat behavior.

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 short sentences with the direction convention front-loaded and zero filler.

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 simple one-parameter input tool with annotations covering safety and no output schema, the definition covers direction and target context adequately. Remaining gaps (focus/prerequisite conditions) are minor.

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 0% and the single 'amount' parameter only exposes a -50..50 range with no description. The description supplies the crucial missing semantics ('positive = up'), which is exactly what the schema omits, though it doesn't state units or step granularity.

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

Purpose4/5

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

States a specific verb ('Scroll') and resource ('the wheel'), and adds sign semantics ('positive = up'). It is distinguishable from siblings like mouse_move and click, though it doesn't explicitly contrast with them.

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 clause 'NUI lists respond to it' implies a usage context but gives no when-to-use vs alternatives guidance, no prerequisite such as needing an open NUI or focused window, and no exclusions.

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