fivem-mcp-server

by ziyacivan

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Release held key(s)

release_key

Release a held key or all held keys to stop simulated key presses from staying active during FiveM server testing.

Instructions

Release one held key, or all of them with key='all'.

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": {
      "key": "<key>"
    },
    "name": "release_key"
  }
}

Input Schema

Name	Required	Description	Default
`key`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Oct 17, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation profile is covered structurally. The description usefully discloses the 'all' sentinel behavior, which the schema does not, but says nothing about what happens if the key is not currently held or about failure 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?

A single sentence, zero filler, with the scope constraint ('all') front-loaded and easy to scan. Nothing extraneous.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter mutation tool with annotations covering safety, the description is close to adequate but omits error/edge behavior (e.g. releasing a key that is not held) and does not hint at the result. Not deficient, but not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single 'key' parameter, so the description must carry the semantics. It does add a meaningful sentinel value (key='all') that the bare string schema lacks, but leaves the format for individual key names unspecified.

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 (release) and resource (held key) plus the 'all' scope, so the action is unambiguous. It does not explicitly contrast itself with the sibling hold_key/press_key, so sibling differentiation is left to inference.

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 phrase 'release one held key' implies this is the inverse of hold_key, and the key='all' note conveys a usage option. However, there is no explicit when-to-use or when-not-to-use guidance relative to the alternatives.

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